Apparatus, system and method of cellular network communications corresponding to a non-cellular network

ABSTRACT

Some demonstrative embodiments include devices, systems and/or cellular network communications corresponding to a non-cellular network. For example, an Evolved Node B (eNB) may be configured to transmit to a User Equipment (UE) at least one configuration message to configure one or more measurements to be performed by the UE with respect to at least Wireless-Local-Area-Network (WLAN), to receive from the UE at least one report message including measurement information corresponding to the WLAN, to trigger the UE to start or stop offloading to the WLAN, and/or to transmit to the UE network assistance information corresponding to the WLAN.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 61/721,436 entitled “AdvancedWireless Communication Systems and Techniques”, filed Nov. 1, 2012, U.S.Provisional Patent Application No. 61/771,698 entitled “AdvancedWireless Communication Systems and Techniques”, filed Mar. 1, 2013, andU.S. Provisional Patent Application No. 61/808,597 entitled “AdvancedWireless Communication Systems and Techniques”, filed Apr. 4, 2013, theentire disclosures of all of which are incorporated herein by reference.

TECHNICAL FIELD

Some embodiments described herein generally relate to cellular networkcommunications corresponding to a non-cellular network.

BACKGROUND

A wireless communication device, e.g., a mobile device, may beconfigured to utilize multiple wireless communication technologies.

For example, a User Equipment (UE) device may be configured to utilize acellular connection, e.g., a Long Term Evolution (LTE) cellularconnection, as well as a wireless-local-area-network (WLAN) connection,e.g., a Wireless-Fidelity (WiFi) connection.

The UE may be configured to automatically utilize a WiFi connection, forexample, as long as a Wi-Fi signal received by the UE is strong enough.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a sequence diagram ofcommunicating Wireless Local Area Network (WLAN) measurement informationand network selection of a User Equipment (UE) at a Connected state, inaccordance with some demonstrative embodiments.

FIG. 3 is a schematic illustration of a sequence diagram ofcommunicating WLAN measurement information and network selection of a UEat an Idle state, in accordance with some demonstrative embodiments.

FIG. 4 is a schematic illustration of a sequence diagram ofcommunicating network selection assistance information between a nodeand a UE, in accordance with some demonstrative embodiments.

FIG. 5 is a schematic flow-chart illustration of a method of networkselection, in accordance with some demonstrative embodiments.

FIG. 6 is a schematic illustration of a product, in accordance with somedemonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment,” “an embodiment,” “demonstrativeembodiment,” “various embodiments,” etc., indicate that theembodiment(s) so described may include a particular feature, structure,or characteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a Smartphone device, a server computer, a handheld computer, ahandheld device, a Personal Digital Assistant (PDA) device, a handheldPDA device, an on-board device, an off-board device, a hybrid device, avehicular device, a non-vehicular device, a mobile or portable device, aconsumer device, a non-mobile or non-portable device, a wirelesscommunication station, a wireless communication device, a wirelessAccess Point (AP), a wired or wireless router, a wired or wirelessmodem, a video device, an audio device, an audio-video (A/V) device, awired or wireless network, a wireless area network, a cellular network,a cellular node, a Wireless Local Area Network (WLAN), a Multiple InputMultiple Output (MIMO) transceiver or device, a Single Input MultipleOutput (SIMO) transceiver or device, a Multiple Input Single Output(MISO) transceiver or device, a device having one or more internalantennas and/or external antennas, Digital Video Broadcast (DVB) devicesor systems, multi-standard radio devices or systems, a wired or wirelesshandheld device, e.g., a Smartphone, a Wireless Application Protocol(WAP) device, vending machines, sell terminals, and the like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Long Term Evolution (LTE)specifications (including “RAN2 RRC—3GPP TS 36.331: Evolved UniversalTerrestrial Radio Access (E-UTRA); Radio Resource Control (RRC);Protocol specification”; “RAN3 X2—3GPP TS 36.423: Evolved UniversalTerrestrial Radio Access Network (E-UTRAN); X2 Application Protocol(X2AP)”; 3GPP TS 23.401 General Packet Radio Service (GPRS) enhancementsfor Evolved Universal Terrestrial Radio Access Network (E-UTRAN)access”; and “3GPP TS 36.413 Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN); S1 Application Protocol (S1AP)”) and/or futureversions and/or derivatives thereof, devices and/or networks operatingin accordance with existing Wireless-Gigabit-Alliance (WGA)specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHYSpecification Version 1.1, April 2011, Final specification) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012),and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing IEEE 802.16 standards(IEEE-Std 802.16, 2009 Edition, Air Interface for Fixed BroadbandWireless Access Systems; IEEE-Std 802.16e, 2005 Edition, Physical andMedium Access Control Layers for Combined Fixed and Mobile Operation inLicensed Bands; amendment to IEEE Std 802.16-2009, developed by TaskGroup m) and/or future versions and/or derivatives thereof, devicesand/or networks operating in accordance with existing WirelessHD™specifications and/or future versions and/or derivatives thereof, unitsand/or devices which are part of the above networks, and the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM(OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA),Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA),Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extendedGPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation(MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System(GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB),Global System for Mobile communication (GSM), second generation (2G),2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, LongTerm Evolution (LTE) cellular system, LTE advance cellular system,High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink PacketAccess (HSUPA), High-Speed Packet Access (HSPA), HSPA+, Single CarrierRadio Transmission Technology (1×RTT), Evolution-Data Optimized (EV-DO),Enhanced Data rates for GSM Evolution (EDGE), and the like. Otherembodiments may be used in various other devices, systems and/ornetworks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a wirelesscommunication signal includes transmitting the wireless communicationsignal and/or receiving the wireless communication signal. For example,a wireless communication unit, which is capable of communicating awireless communication signal, may include a wireless transmitter totransmit the wireless communication signal to at least one otherwireless communication unit, and/or a wireless communication receiver toreceive the wireless communication signal from at least one otherwireless communication unit.

Some demonstrative embodiments are described herein with respect to aLTE cellular system. However, other embodiments may be implemented inany other suitable cellular network, e.g., a 3G cellular network, a 4Gcellular network, a 5G cellular network, a WiMax cellular network, andthe like.

Some demonstrative embodiments are described herein with respect to aWLAN system. However, other embodiments may be implemented in any othersuitable non-cellular network.

Some demonstrative embodiments may be used in conjunction with aHeterogeneous Network (HetNet), which may utilize a deployment of a mixof technologies, frequencies, cell sizes and/or network architectures,e.g., including cellular, mmWave, and/or the like. In one example, theHetNet may include a radio access network having layers ofdifferent-sized cells ranging from large macrocells to small cells, forexample, picocells and femtocells.

Other embodiments may be used in conjunction with any other suitablewireless communication network.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a dipole antenna, a set of switched beamantennas, and/or the like.

The term “cell”, as used herein, may include a combination of networkresources, for example, downlink and optionally uplink resources. Theresources may be controlled and/or allocated, for example, by a cellularnode (also referred to as a “base station”), or the like. The linkingbetween a carrier frequency of the downlink resources and a carrierfrequency of the uplink resources may be indicated in system informationtransmitted on the downlink resources.

The phrase “access point” (AP), as used herein, may include an entitythat includes a station (STA) and provides access to distributionservices, via the Wireless Medium (WM) for associated STAs.

The term “station” (STA), as used herein, may include any logical entitythat is a singly addressable instance of a medium access control (MAC)and a physical layer (PHY) interface to the WM.

The phrases “directional multi-gigabit (DMG)” and “directional band”(DBand), as used herein, may relate to a frequency band wherein theChannel starting frequency is above 56 GHz.

The phrases “DMG STA” and “mmWave STA (mSTA)” may relate to a STA havinga radio transmitter, which is operating on a channel that is within theDMG band.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100, in accordance with some demonstrativeembodiments.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude one or more wireless communication devices capable ofcommunicating content, data, information and/or signals via one or morewireless mediums 108. For example, system 100 may include at least oneUser Equipment (UE) 102 capable of communicating with one or morewireless communication networks, e.g., as described below.

Wireless mediums 108 may include, for example, a radio channel, acellular channel, an RF channel, a Wireless Fidelity (WiFi) channel, anIR channel, and the like. One or more elements of system 100 mayoptionally be capable of communicating over any suitable wiredcommunication links.

In some demonstrative embodiments, system 100 may include at least onecellular network 103, e.g., a cell controlled by a node 104.

In some demonstrative embodiments, system 100 may include a non-cellularnetwork 107, for example, a WLAN, e.g., a Basic Service Set (BSS),managed by an Access Point (AP) 106.

In some demonstrative embodiments, non-cellular network 107 may at leastpartially be within a coverage area of node 104. For example, AP 106 maybe within a coverage area of node 104.

In some demonstrative embodiments, node 104 may include an Evolved NodeB (eNB). For example, node 104 may be configured to perform radioresource management (RRM), radio bearer control, radio admission control(access control), connection mobility management, resource schedulingbetween UEs and eNB radios, e.g., Dynamic allocation of resources to UEsin both uplink and downlink, header compression, link encryption of userdata streams, packet routing of user data towards a destination, e.g.,another eNB or an Evolved Packet Core (EPC), scheduling and/ortransmitting paging messages, e.g., incoming calls and/or connectionrequests, broadcast information coordination, measurement reporting,and/or any other operations.

In other embodiments, node 104 may include any other functionalityand/or may perform the functionality of any other cellular node, e.g., aNode B (NB), a base station or any other node or device.

In some demonstrative embodiments, UE 102 may include, for example, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a mobile internet device, a handheld computer, a handhelddevice, a storage device, a PDA device, a handheld PDA device, anon-board device, an off-board device, a hybrid device (e.g., combiningcellular phone functionalities with PDA device functionalities), aconsumer device, a vehicular device, a non-vehicular device, a mobile orportable device, a mobile phone, a cellular telephone, a PCS device, amobile or portable GPS device, a DVB device, a relatively smallcomputing device, a non-desktop computer, a “Carry Small Live Large”(CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC),a Mobile Internet Device (MID), an “Origami” device or computing device,a video device, an audio device, an A/V device, a gaming device, a mediaplayer, a Smartphone, or the like.

In some demonstrative embodiments, UE 102, node 104 and/or AP 106 mayinclude one or more wireless communication units to perform wirelesscommunication between UE 102, node 104, AP 106 and/or with one or moreother wireless communication devices, e.g., as described below. Forexample, UE 102 may include a wireless communication unit 110 and/ornode 104 may include a wireless communication unit 130.

In some demonstrative embodiments, wireless communication units 110 and130 may include, or may be associated with, one or more antennas. In oneexample, wireless communication unit 110 may be associated with at leasttwo antennas, e.g., antennas 112 and 114, or any other number ofantennas, e.g., one antenna or more than two antennas; and/or wirelesscommunication unit 130 may be associated with at least two antennas,e.g., antennas 132 and 134, or any other number of antennas, e.g., oneantenna or more than two antennas.

In some demonstrative embodiments, antennas 112, 114, 132 and/or 134 mayinclude any type of antennas suitable for transmitting and/or receivingwireless communication signals, blocks, frames, transmission streams,packets, messages and/or data. For example, antennas 112, 114,132 and/or134 may include any suitable configuration, structure and/or arrangementof one or more antenna elements, components, units, assemblies and/orarrays. For example, antennas 112, 114, 132 and/or 134 may include aphased array antenna, a dipole antenna, a single element antenna, a setof switched beam antennas, and/or the like.

In some embodiments, antennas 112, 114, 132 and/or 134 may implementtransmit and receive functionalities using separate transmit and receiveantenna elements. In some embodiments, antennas 112, 114, 132 and/or 134may implement transmit and receive functionalities using common and/orintegrated transmit/receive elements.

In some demonstrative embodiments, wireless communication unit 130 mayinclude at least one radio 142 and at least one controller 144 tocontrol communications performed by radio 142, and/or wirelesscommunication unit 110 may include at least one radio 143 and at leastone controller 145 to control communications performed by radio 143. Forexample, radios 142 and/or 143 may include one or more wirelesstransmitters, receivers and/or transceivers able to send and/or receivewireless communication signals, RF signals, frames, blocks, transmissionstreams, packets, messages, data items, and/or data.

In some demonstrative embodiments, radios 142 and/or 143 may include amultiple input multiple output (MIMO) transmitters receivers system (notshown), which may be capable of performing antenna beamforming methods,if desired. In other embodiments, radios 142 and/or 143 may include anyother transmitters and/or receivers.

In some demonstrative embodiments, radios 142 and/or 143 may include aturbo decoder and/or a turbo encoder (not shown) for encoding and/ordecoding data bits into data symbols, if desired. In other embodiments,radios 142 and/or 143 may include any other encoder and/or decode.

In some demonstrative embodiments, radios 142 and/or 143 may includeOFDM and/or SC-FDMA modulators and/or demodulators (not shown)configured to communicate OFDM signals over downlink channels, e.g.,between node 104 and UE 102, and SC-FDMA signals over uplink channels,e.g., between UE 102 and node 104. In other embodiments, radios 142and/or 143 may include any other modulators and/or demodulators.

In some demonstrative embodiments, wireless communication unit 110 mayestablish a WLAN link with AP 106. For example, wireless communicationunit 110 may perform the functionality of one or more STAs, e.g., one ormore WiFi STAs, WLAN STAs, and/or DMG STAs. The WLAN link may include anuplink and/or a downlink. The WLAN downlink may include, for example, aunidirectional link from AP 106 to the one or more STAs or aunidirectional link from a Destination STA to a Source STA. The uplinkmay include, for example, a unidirectional link from a STA to AP 106 ora unidirectional link from the Source STA to the Destination STA.

In some demonstrative embodiments, UE 102, node 104 and/or AP 106 mayalso include, for example, one or more of a processor 124, an input unit116, an output unit 118, a memory unit 120, and a storage unit 122. UE102, node 104 and/or AP 106 may optionally include other suitablehardware components and/or software components. In some demonstrativeembodiments, some or all of the components of one or more of UE 102,node 104 and/or AP 106 may be enclosed in a common housing or packaging,and may be interconnected or operably associated using one or more wiredor wireless links. In other embodiments, components of one or more of UE102, node 104 and/or AP 106 may be distributed among multiple orseparate devices.

Processor 124 includes, for example, a Central Processing Unit (CPU), aDigital Signal Processor (DSP), one or more processor cores, asingle-core processor, a dual-core processor, a multiple-core processor,a microprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 124 executes instructions,for example, of an Operating System (OS) of UE 102, node 104 and/or AP106 and/or of one or more suitable applications.

Input unit 116 includes, for example, a keyboard, a keypad, a mouse, atouch-screen, a touch-pad, a track-ball, a stylus, a microphone, orother suitable pointing device or input device. Output unit 118includes, for example, a monitor, a screen, a touch-screen, a flat paneldisplay, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display(LCD) display unit, a plasma display unit, one or more audio speakers orearphones, or other suitable output devices.

Memory unit 120 includes, for example, a Random Access Memory (RAM), aRead Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM(SD-RAM), a flash memory, a volatile memory, a non-volatile memory, acache memory, a buffer, a short term memory unit, a long term memoryunit, or other suitable memory units. Storage unit 122 includes, forexample, a hard disk drive, a floppy disk drive, a Compact Disk (CD)drive, a CD-ROM drive, a DVD drive, or other suitable removable ornon-removable storage units. Memory unit 120 and/or storage unit 122,for example, may store data processed by UE 102, node 104 and/or AP 106.

In some demonstrative embodiments, UE 102 may be configured utilize acellular connection, e.g., a Long Term Evolution (LTE) cellularconnection, a Universal Mobile Telecommunications System (UMTS)connection or any other cellular connection, to communicate with node104, and a WLAN connection, e.g., a Wireless-Fidelity (WiFi) connectionor any other WLAN connection, to communicate with AP 106.

In some demonstrative embodiments, one or more elements of system 100may perform the functionality of a HetNet, which may utilize adeployment of a mix of technologies, frequencies, cell sizes and/ornetwork architectures, for example, including cellular, WLAN, and/or thelike.

For example, the HetNet may be configured to provide a service through afirst wireless communication environment, e.g., a cellular network, andto maintain the service when switching to another communicationenvironment, e.g., WLAN. The HetNet architecture may enable utilizing amixture of wireless communication environments, e.g., a WLAN environmentand a cellular environment, for example, to optimally respond to rapidchanges in customer demand, reduce power consumption, reduce cost,increase efficiency and/or achieve any other benefit.

In one example, system 100 may utilize a Multi-tier, Multi-Radio AccessTechnology (Multi-RAT) Het-Net architecture, including a tier of smallcells, e.g., pico, femto, relay stations, WiFi APs, and the like,overlaid on top of a macro cellular deployment to augment networkcapacity.

In another example, system 100 may utilize Multi-RAT small cellsintegrating multiple radios such as WiFi and 3GPP air interfaces in asingle infrastructure device.

In other embodiments, system 100 may implement any other architectureand/or deployment.

In some demonstrative embodiments, utilizing the WLAN connection as adefault connection, e.g., as long as UE 102 receives from AP 106 astrong enough signal, may result in an increase in the congestion of theWLAN, e.g., if a large number of UEs connect by default to the same AP,which in turn may result in a decrease of throughput over the WLANconnection between UE 102 and AP 106.

In some demonstrative embodiments, UE 102, node 104 and/or AP 106 may beconfigured to enable selective connection of UE 102 to the WLAN or thecellular network, for example, based on one or more criteria and/orparameters, e.g., as described in detail below.

In some demonstrative embodiments, the selective connection between UE102 and node 104 or AP 106 may enable, for example, load balancingbetween the WLAN and the cellular network.

In some demonstrative embodiments, UE 102, node 104 and/or AP 106 may beconfigured to enable a network-centric (also referred to as “networkcontrolled”) access network selection scheme, in which node 104 and/orone or more other cellular network elements select an access network tobe utilized by UE 102. For example, node 104 may be configured tocontrol access network selection for UE 102.

In one example, node 104 may be configured to selectively trigger UE 102to start or stop offloading to a WLAN, for example, the WLAN controlledby AP 106, e.g., as described below.

In some demonstrative embodiments, UE 102, node 104 and/or AP 106 may beconfigured to enable a UE-centric (also referred to as “UE controlled”)access network selection scheme, in which UE 102 may select an accessnetwork to be utilized by UE 102. For example, UE 102 may select theaccess network based on network assistance information, which may bereceived from node 104 and/or based on any other information and/orcriteria from any other element of system 100, e.g., as described below.

In some demonstrative embodiments, cooperation between cellular networksand WLAN networks, e.g., between node 104 and AP 106, may enable makingnetwork assignment decisions which maximize overall system performance,e.g., in terms of load, throughput, and the like. Additionally oralternatively, the cellular networks and WLAN networks may cooperate toprovide optimal network assistance information, which may enablesteering users towards decisions that improve system-wide performance.

However, some systems, e.g., deployments for multi-RAT Het-Nets, mayinclude distributed deployments wherein components of the cellularnetwork, e.g., node 104, and components of the non-cellular network,e.g., AP 106, may not necessarily be co-located and/or may notnecessarily have direct network interfaces, e.g., a network interfacebetween cell 103 and AP 106 may not exist. There may be minimal or evenno degree of cooperation between distributed cells and/or networks and,as a result, the efficacy of network assistance transmitted to UE 102may be limited.

Additionally or alternatively, cell selection schemes for distributeddeployments, which may be based on power and/or signal strength metrics,e.g., Signal-to-Interference-Plus-Noise Ratio (SINR) or Received SignalStrength Indication (RSSI), may not fully account of network loading orperformance conditions.

In some demonstrative embodiments, network assistance information mayinclude or may be provided in the form of “network load”, which mayimprove UE-based network selection. Additionally or alternately, a levelof cooperation between the WLAN and cellular networks may be improvedthrough UE assistance, wherein the UEs can measure local informationfrom other cells in their vicinity and make the information available tothe distributed cells in the network.

Some demonstrative embodiments may include mechanisms, which may improvenetwork selection and/or association, for example, for distributedmulti-RAT Het-Net deployments or any other systems. For example, system100 may include a WLAN deployment within an operator managedheterogeneous network, for example, wherein there are limited or even nostandardized network interfaces between node 104 and AP 106. Accordingto these embodiments, node 104 and AP 106 may cooperate through UEassistance (“the UE-assisted network selection”), e.g., by UE 102.

In some demonstrative embodiments, the UE-assisted network selection mayenable movement of UE 102 to and from WLAN and cellular networks, forexample, when UE is operating in a Radio-Resource Control (RRC)connected mode or a RRC Idle mode, e.g., as described below.

In some demonstrative embodiments, node 104 may be configured to controlnetwork selection and/or traffic steering of UE 102 between WLANnetworks, e.g., WLAN 107, and cellular networks, e.g., cell 103, e.g.,as described below.

In one example, node 104 may be configured to control network selectionand/or traffic steering of UE 102 between the WLAN networks and thecellular networks through direct network initiated triggers, e.g., asdescribed below.

In another example, node 104 may be configured to control networkselection and/or traffic steering of UE 102 between the WLAN networksand the cellular networks through assignment messaging, e.g., asdescribed below.

In another example, node 104 may be configured to control networkselection and/or traffic steering of UE 102 between the WLAN networksand the cellular networks by using network assistance to assist, steerand/or control UE network selection, e.g., as described below.

Some demonstrative embodiments may be implemented, for example, withoutrequiring any changes for WLAN interfaces, e.g., even if UE 102 isunable to provide cellular network statistics, e.g., of cell 103, toWLAN APs, e.g., to AP 106.

In some demonstrative embodiments, UE 102 may transmit to node 104measurement information corresponding to WLAN 107, e.g., as describedbelow.

In some demonstrative embodiments, node 104 may configure themeasurements performed by UE 102, for example, using one or moreconfiguration messages, which may be transmitted from node 104 to UE 102via the cellular link between UE 102 and node 104, e.g., as describedbelow.

For example, node 104 may transmit to UE 102 at least one configurationmessage to configure one or more measurements to be performed by UE 102with respect to WLAN 107, e.g., as described below.

In some demonstrative embodiments, node 104 may request from UE 102information relating to one or more serving WLANs and/or neighboringWLANs, e.g., including WLAN 107, for example, a Neighboring WLANidentifiers report, a Neighboring WLAN signal strength/rate report, aNeighboring WLAN signal strength/rate report, e.g., based on aBSS_Load_Info, “Serving” WLAN Load information, e.g., based on aBSS_Load_Info broadcast by AP 106, a “Serving” WLAN network overloadindication, a UE current WLAN QoS indicator, e.g., per Quality ofService (QoS) Class Indicator (QCI) identifiers, a UE WLAN preferenceindicator, other “Detected WLAN” cells for which explicit measurementswere not solicited, and/or any other information, e.g., as describedbelow.

In some demonstrative embodiments, UE 102 may transmit to node 104 areport message including the measurement information corresponding toWLAN 107, e.g., as described below.

In some demonstrative embodiments, UE may transmit the report message tonode 104, when UE 102 is at the RRC Connected state, e.g., as describedbelow.

In some demonstrative embodiments, it may be easier for UE 102 to reportthe measurement information to node 104, for example, when UE 102 is inthe RRC connected state.

In some demonstrative embodiments, node 104 may configure themeasurements and/or the report messages by UE 102, for example, via RRCsignaling messages. In one example, a RRCConnectionReconfigurationmessage and/or measConfig information elements may be used for settingWLAN specific measurements and associated triggers for reporting themeasurements, e.g., as described below. UE 102 may, for example, respondby sending a MeasurementReport via aRRCConnectionReconfigurationComplete message. Other messages, e.g.,RRCConnectionReestablishment and/or RRCConnectionRestablishmentComplete,may be used for this procedure.

In some demonstrative embodiments, UE 102 may transmit the reportmessage to node 104, when UE 102 is at the RRC Idle state, e.g., asdescribed below.

In some demonstrative embodiments, node 104 may configure WLANmeasurements for UE 102, e.g., with respect to WLAN 107.

In some demonstrative embodiments, node 104 may transmit to UE 102 theconfiguration message including one or more parameters corresponding toat least one WLAN, for which measurements are requested.

In some demonstrative embodiments, the configuration message may includea Measurement Information Element (IE) including the at least oneparameter, e.g., as described below.

In one example, the configuration message may include at least oneidentifier of the WLAN, at least one frequency band of the WLAN, atleast one frequency channel of the WLAN, and/or any other parameter,e.g., as described below.

In some demonstrative embodiments, the identifier of the WLAN mayinclude, for example, a Service Set Identification (SSID), an ExtendedSSID (ESSID), a Basic SSID (SSID), a Roaming Consortium, a HotspotOperator Friendly Name, a Network Access Identifier (NAI) Home Realm, aMobility Domain, and/or any additional or alternative identifier of theWLAN, e.g., as described below.

In some demonstrative embodiments, node 104 may use RRC signaling toconfigure the WLAN measurements for UE 102.

In some demonstrative embodiments, node 104 may configure the WLANmeasurements using a RRCConnectionReconfiguration message, e.g., asdescribed below. In other embodiments any other message and/orinformation element may be used.

In some demonstrative embodiments, node 104 may transmit to UE 102 aRRCConnectionReconfiguration message identifying one or more inter-RATmeasurements of WLAN frequencies.

In some demonstrative embodiments, node 104 may use theRRCConnectionReconfiguration message to request UE 102 to measure, e.g.,using a WLAN baseband of radio 143, and to report informationcorresponding to one or more WLANs, e.g., WLAN 107, which may be, forexample, suitable candidates for UE mobility to WLAN, e.g., of UE 102and/or one or more other UEs within cell 103.

In some demonstrative embodiments, the RRCConnectionReconfiguration mayinclude an IE, e.g., an optional “MeasConfig” IE, which may include alist of measurement objects. The MeasConfig IE may include for example,a measObjectToAddModList IE, e.g., as follows:

-- ASN1START MeasConfig ::= SEQUENCE { -- Measurement objectsmeasObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need ONmeasObjectToAddModList MeasObjectToAddModList OPTIONAL, -- Need ON --Reporting configurations reportConfigToRemoveListReportConfigToRemoveList OPTIONAL, -- Need ON reportConfigToAddModListReportConfigToAddModList OPTIONAL, -- Need ON -- Measurement identitiesmeasIdToRemoveList MeasIdToRemoveList OPTIONAL, -- Need ONmeasIdToAddModList MeasIdToAddModList OPTIONAL, -- Need ON -- Otherparameters quantityConfig QuantityConfig OPTIONAL, -- Need ONmeasGapConfig MeasGapConfig OPTIONAL, -- Need ON s-Measure RSRP-RangeOPTIONAL, -- Need ON preRegistrationInfoHRPD PreRegistrationInfoHRPDOPTIONAL, -- Need OP speedStatePars CHOICE { release NULL, setupSEQUENCE { mobilityStateParameters MobilityStateParameters,timeToTrigger-SF SpeedStateScaleFactors } } OPTIONAL, -- Need ON ... }MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxMeasId)) OF MeasIdMeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxObjectId)) OFMeasObjectId ReportConfigToRemoveList ::= SEQUENCE (SIZE(1..maxReportConfigId)) OF ReportConfigId -- ASN1STOP

In some demonstrative embodiments, the measObjectToAddModList IE mayinclude, for example, measurement objects corresponding to one or more,e.g., different RATs.

In some demonstrative embodiments, the measObjectToAddModList IE mayinclude, for example, a WLAN measurement object, denoted measObjectWLAN,e.g., as follows:

-- ASN1START MeasObjectToAddModList ::= SEQUENCE (SIZE (1..maxObjectId))OF MeasObjectToAddMod MeasObjectToAddMod ::= SEQUENCE { measObjectIdMeasObjectId, measObject CHOICE { measObjectEUTRA MeasObjectEUTRA,measObjectUTRA MeasObjectUTRA, measObjectGERAN MeasObjectGERAN,measObjectCDMA2000 MeasObjectCDMA2000, measObjectWLAN MeasObjectWLAN,... } } -- ASN1STOP

In some demonstrative embodiments, node 104 may use the measObjectWLANIE to request UE 102 to perform one or more WLAN related measurements,e.g., as described below.

In some demonstrative embodiments, the MeasObjectWLAN IE may include oneor more parameters corresponding to one or more WLANs, for which UE 102is to perform measurements. For example, the MeasObjectWLAN IE mayinclude a SSID list; an ESSID list; a BSSID list; a frequency band,e.g., 2.4 GHz or 5 GHz and the like; a Channel and/or frequency list;one or more parameters defined in any suitable WLAN Specificationsand/or Protocols, e.g., a Roaming Consortium, a Hotspot OperatorFriendly Name, a NAI Home Realm, a Mobility Domain, and/or any otherparameter.

In one example, the MeasObjectWLAN IE may include, for example, thefollowing information:

-- ASN1START MeasObjectWLAN ::= SEQUENCE { channel WLANChannel OPTIONAL,ssidsToRemoveList CellIndexList OPTIONAL, ssidsToAddModListSSIDsToAddModList OPTIONAL, } SSIDsToAddModList ::= SEQUENCE (SIZE(1..maxCellMeas)) OF SSIDsToAddMod SSIDsToAddMod ::= SEQUENCE {cellIndex INTEGER (1..maxCellMeas), ssid SSID, bssid BSSID OPTIONAL, }SSID ::= OCTET STRING (SIZE (32)) BSSID ::= BIT STRING (SIZE (48)) --ASN1STOP

In some demonstrative embodiments, node 104 may transmit to UE 102 theconfiguration message including reporting configuration informationdefining a reporting criterion defining a criterion to trigger UE 102 tosend the report message, and/or a reporting format defining themeasurement information to be reported by UE 102, e.g., as describedbelow.

In some demonstrative embodiments, the reporting criterion may define aperiodical reporting event, e.g., to trigger UE 102 to report the WLANmeasurement information periodically.

In other demonstrative embodiments, the reporting criterion may define asingle reporting event, e.g., to trigger a single report of the WLANmeasurement information.

In some demonstrative embodiments, the reporting criterion may include acriterion related to WLAN network availability, a Received SignalStrength Indicator (RSSI) threshold, a Received Channel Power Indicator(RCPI) threshold, a Received Power Indicator (RPI) threshold, a ReceivedSignal to Noise Indicator (RSNI) threshold, a WLAN channel utilization,and/or any other additional or alternative parameter to trigger UE 102to report the WLAN measurement information, e.g., as described below. Insome demonstrative embodiments, node 104 may transmit the reportingconfiguration information as part of an IE, e.g., a ReportConfigInterRATIE, which may specify criteria for triggering of an inter-RATmeasurement reporting event. For example, an inter-RAT measurementreporting event may be labeled by a label, denoted BN, N=1, 2, . . . n,wherein n denotes a number of the inter-RAT measurement reportingevents.

In one example, an event B1 may be defined to trigger a report when aparameter of a WLAN Neighbor, e.g., WLAN 107, becomes better than anabsolute threshold, denoted Threshold; and/or an event B2 may be definedto trigger a report when a parameter of a LTE cell, e.g., cell 103,becomes worse than a first absolute threshold, denoted Threshold1, and aparameter of a WLAN neighbor, e.g., WLAN 107, becomes better than asecond absolute threshold, denoted Threshold2. The b1 and b2 eventthresholds may be expressed, for example, as an unsigned binary numberequal to [−2×10 log 10 E_(c)/I₀] in units of 0.5 dB, or in any otherform. For example, a field bN-ThresholdM may define a threshold to beused in inter-RAT measurement report triggering condition for eventnumber bN. If multiple thresholds are defined for event number bN, thethresholds may be differentiated by M.

For example, the reporting configuration information may defineThreshold value to configure UE 102 to report WLAN measurements to node104, for example, when a signal strength of AP 106 is high enough, e.g.,higher than the Threshold value. UE 102 may receive the high signalstrength from AP 106, for example, when UE 102 is in relatively goodWLAN coverage. In another example, the reporting configurationinformation may trigger UE 102 to report WLAN measurements to node 104,for example, when UE 102 has relatively bad LTE coverage, e.g., when anLTE measurement is lesser than the Threshold1, and while UE 102 hasrelatively good WLAN coverage, e.g., the WLAN measurement is greaterthan the Threshold2.

In some demonstrative embodiments, the ReportConfigInterRAT IE mayinclude the following fields:

-- ASN1START ReportConfigInterRAT ::= SEQUENCE { triggerType CHOICEevent SEQUENCE { eventId CHOICE { eventB1 SEQUENCE { b1-Threshold CHOICE{ b1-ThresholdUTRA ThresholdUTRA, b1-ThresholdGERAN ThresholdGERAN,b1-ThresholdCDMA2000 ThresholdCDMA2000, b1-ThresholdWLAN ThresholdWLAN }}, eventB2 SEQUENCE { b2-Threshold1 ThresholdEUTRA, b2-Threshold2 CHOICE{ b2-Threshold2UTRA ThresholdUTRA, b2-Threshold2GERAN ThresholdGERAN,b2-Threshold2CDMA2000 ThresholdCDMA2000, b1-ThresholdWLAN ThresholdWLAN} }, ... }, hysteresis Hysteresis, timeToTrigger TimeToTrigger },periodical SEQUENCE { purpose ENUMERATED { reportStrongestCells,reportStrongestCellsForSON, reportCGI} } }, maxReportCells INTEGER(1..maxCellReport), reportInterval ReportInterval, reportAmountENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, ..., [[si-RequestForHO-r9 ENUMERATED {setup} OPTIONAL -- Cond reportCGI ]], [[reportQuantityUTRA-FDD-r10 ENUMERATED {both} OPTIONAL -- Need OR ]], [[includeLocationInfo-r11 ENUMERATED {true} OPTIONAL -- Need OR ]] }ThresholdUTRA ::= CHOICE{ utra-RSCP INTEGER (−5..91), utra-EcN0 INTEGER(0..49) } ThresholdGERAN ::= INTEGER (0..63) ThresholdCDMA2000 ::=INTEGER (0..63) ThresholdWLAN ::= CHOICE{ wlan-rssi INTEGER (0..255),wlan-rcpi INTTEGER (0..255), wlan-rsni INTTEGER (0..255),wlan-channel-utilization INTTEGER (0..255) } -- ASN1STOP

In one example, one or more fields of the ReportConfigInterRAT IE may bedefined, e.g., as follows:

ReportConfigInterRAT field descriptions bN-ThresholdM Threshold to beused in inter RAT measurement report triggering condition for eventnumber bN. If multiple thresholds are defined for event number bN, thethresholds are differentiated by M. eventId Choice of inter-RAT eventtriggered reporting criteria. maxReportCells Max number of cells,excluding the serving cell, to include in the measurement report. Incase purpose is set to reportStrongestCellsForSON only value 1 applies.Purpose reportStrongestCellsForSON applies only in case reportConfig islinked to a measObject set to measObjectUTRA or measObjectCDMA2000.reportAmount Number of measurement reports applicable for triggerTypeevent as well as for triggerType periodical. In case purpose is set toreportCGI or reportStrongestCellsForSON only value 1 applies.reportQuantityUTRA-FDD The quantities to be included in the UTRAmeasurement report. The value both means that both the cpich RSCP andcpich EcN0 quantities are to be included in the measurement report.si-RequestForHO The field applies to the reportCGI functionality, andwhen the field is included, the UE is allowed to use autonomous gaps inacquiring system information from the neighbour cell, applies adifferent value for T321, and includes different fields in themeasurement report. ThresholdGERAN The actual value is IE value - 110dBm. ThresholdUTRA utra-RSCP corresponds to CPICH_RSCP in TS 25.133 [29]for FDD and P-CCPCH_RSCP in TS 25.123 [30] for TDD. utra-EcN0corresponds to CPICH_Ec/No in TS 25.133 [29] for FDD, and is notapplicable for TDD. For utra-RSCP: The actual value is IE value − 115dBm. For utra-EcN0: The actual value is (IE value − 49)/2 dB.ThresholdWLAN wlan-rssi corresponds to receive signal strength indicatorin 802.11- 2012 wlan-rcpi corresponds to received channel powerindicator in 802.11- 2012 wlan-rsni corresponds to received signal tonoise indicator in 802.11- 2012 wlan-channel-utilization corresponds tochannel utilization in 802.11- 2012 timeTo Trigger Time during whichspecific criteria for the event needs to be met in order to trigger ameasurement report.

In some demonstrative embodiments, node 104 may use an IE to define toUE 102 what parameters are to be measured with respect to the one ormore WLANs.

In one example, node 104 may use the QuantityConfig IE to specify whatWLAN measurements are to be performed by UE 102 and/or what parametersare to be included in the measurement information to be reported by UE102.

For example, the QuantityConfig IE may specify measurement quantitiesand/or filtering coefficients, e.g., layer 3 filtering coefficients ofinter-RAT measurements, e.g., as follows:

QuantityConfig information element -- ASN1START QuantityConfig ::=SEQUENCE { quantityConfigEUTRA QuantityConfigEUTRA OPTIONAL, -- Need ONquantityConfigUTRA QuantityConfigUTRA OPTIONAL, -- Need ONquantityConfigGERAN QuantityConfigGERAN OPTIONAL, -- Need ONquantityConfigCDMA2000 QuantityConfigCDMA2000 OPTIONAL, -- Need ON ...,[[ quantityConfigUTRA-v1020 QuantityConfigUTRA-v1020 OPTIONAL -- Need ON]] [[ quantityConfigWLAN QuantityConfigWLAN OPTIONAL -- Need ON ]] }QuantityConfigEUTRA ::= SEQUENCE { filterCoefficientRSRPFilterCoefficient DEFAULT fc4, filterCoefficientRSRQ FilterCoefficientDEFAULT fc4 } QuantityConfigUTRA ::= SEQUENCE { measQuantityUTRA-FDDENUMERATED {cpich-RSCP, cpich-EcN0}, measQuantityUTRA-TDD ENUMERATED{pccpch-RSCP}, filterCoefficient FilterCoefficient DEFAULT fc4 }QuantityConfigUTRA-v1020 ::= SEQUENCE { filterCoefficient2-FDD-r10FilterCoefficient DEFAULT fc4 } QuantityConfigGERAN ::= SEQUENCE {measQuantityGERAN ENUMERATED {rssi}, filterCoefficient FilterCoefficientDEFAULT fc2 } QuantityConfigCDMA2000 ::= SEQUENCE { measQuantityCDMA2000ENUMERATED {pilotStrength, pilotPnPhaseAndPilotStrength} }QuantityConfigWLAN ::= SEQUENCE { measQuantityWLAN ENUMERATED {rssi,rsni, rcpi, channel-utilization }, filterCoefficient FilterCoefficientDEFAULT fc4 } -- ASN1S TOP

In one example, one or more fields of the QuantityConfig IE may bedefined, e.g., as follows:

Quantity Config field descriptions filterCoefficient2-FDD Specifies thefiltering coefficient used for the UTRAN FDD measurement quantity, whichis not included in measQuantityUTRA- FDD, when reportQuantityUTRA-FDD ispresent in ReportConfigInterRAT. filterCoefficientRSRP Specifies thefiltering coefficient used for RSRP. filterCoefficientRSRQ Specifies thefiltering coefficient used for RSRQ. measQuantityCDMA2000 Measurementquantity used for CDMA2000 measurements. pilotPnPhaseAndPilotStrength isonly applicable for MeasObjectCDMA2000 of cdma2000-Type = type1XRTT.measQuantityGERAN Measurement quantity used for GERAN measurements.measQuantityUTRA Measurement quantity used for UTRA measurements.quantityConfigCDMA2000 Specifies quantity configurations for CDMA2000measurements. quantityConfigEUTRA Specifies filter configurations forE-UTRA measurements. quantityConfigGERAN Specifies quantity and filterconfigurations for GERAN measurements. quantityConfigUTRA Specifiesquantity and filter configurations for UTRA measurements. FieldquantityConfigUTRA-v1020 is applicable only when reportQuantityUTRA-FDDis configured. quantityConfigWLAN Specifies quantity and filterconfigurations for WLAN measurements.

In some demonstrative embodiments, UE 102 may transmit to node 104 atleast one report message including the measurement informationcorresponding to WLAN 107 and/or one or more other WLANs.

In some demonstrative embodiments, UE 102 may transmit the reportmessage based on the measurement reporting configuration informationdefined by node 104.

In some demonstrative embodiments, UE 102 may transmit the reportmessage to node 104 according to a measurement reporting procedure, forexample, as part of a MeasurementReport RRC message, e.g., as describedbelow, or any other message.

In some demonstrative embodiments, MeasurementReport RRC message mayinclude an IE, e.g., a measResults IE, which may carry measurementresults for neighboring cells, which belong to different RATs. Accordingto these embodiments, the measResults IE may include the WLANmeasurement results.

In some demonstrative embodiments, the WLAN measurement results mayinclude one or more types of information, e.g., including one or more ofthe following parameters and/or any other information:

-   -   1. SSID or ESSID;    -   2. BSSID;    -   3. Other WLAN identifiers, e.g., one or more identifiers as        defined in the HotSpot 2.0 specification, e.g. Roaming        Consortium, Hotspot Operator Friendly Name, NAI Home Realm,        Mobility Domain, and/or any other WLAN identifiers;    -   4. Channel/frequency;    -   5. Privacy and security;    -   6. Receive signal strength indicator (RSSI), e.g., as defined by        IEEE 802.11-2012;    -   7. Received channel power indicator (RCPI), e.g., as defined by        IEEE 802.11-2012;    -   8. Received power indicator (RPI), e.g., as defined by IEEE        802.11-2012;    -   9. Received signal to noise indicator (RSNI), e.g., as defined        by IEEE 802.11-2012;    -   10. Channel traffic, e.g., as defined by IEEE 802.11-2012;    -   11. Channel load, e.g., as defined by IEEE 802.11-2012;    -   12. Noise histogram, e.g., as defined by IEEE 802.11-20121;    -   13. STA statistics, e.g., as defined by IEEE 802.11-2012;    -   14. Location, e.g., as defined by IEEE 802.11-2012;    -   15. Neighbor report, e.g., as defined by IEEE 802.11-2012;    -   16. Link measurement, e.g., as defined by IEEE 802.11-2012;    -   17. BSS Load, e.g., as defined by IEEE 802.11-2012;    -   18. AP Channel Report, e.g., as defined by IEEE 802.11-2012;    -   19. BSS Available Admission Capacity, e.g., as defined by IEEE        802.11-2012;    -   20. BSS AC Access Delay, e.g., as defined by IEEE 802.11-2012;    -   21. Supported rates, e.g., as defined by IEEE 802.11-2012;    -   22. Extended Supported Rates, e.g., as defined by IEEE        802.11-2012; and/or    -   23. Power Constraint, e.g., as defined by IEEE 802.11-2012.

In some demonstrative embodiments, the measurement report IE mayinclude, for example, the following information:

-- ASN1START MeasResults ::= SEQUENCE { measId MeasId, measResultPCellSEQUENCE { rsrpResult RSRP-Range, rsrqResult RSRQ-Range },measResultNeighCells CHOICE { measResultListEUTRA MeasResultListEUTRA,measResultListUTRA MeasResultListUTRA, measResultListGERANMeasResultListGERAN, measResultsCDMA2000 MeasResultsCDMA2000,measResultsListWLAN MeasResultsListWLAN, ... } OPTIONAL, ..., [[measResultForECID-r9 MeasResultForECID-r9 OPTIONAL ]], [[locationInfo-r10 LocationInfo-r10 OPTIONAL, measResultServFreqList-r10MeasResultServFreqList-r10 OPTIONAL ]] } MeasResultListWLAN ::= SEQUENCE(SIZE (1..maxCellReport)) OF MeasResultWLAN MeasResultWLAN ::= SEQUENCE{ ssid SSID, bssid BSSID OPTIONAL, channel WLANChannel OPTIONAL, bssLoadBSSLoad OPTIONAL, channelLoad ChannelLoad OPTIONAL, measResult SEQUENCE{ rcpi RCPI OPTIONAL, rsni RSNI OPTIONAL, ... } } MeasResultListEUTRA::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRAMeasResultEUTRA ::= SEQUENCE { physCellId PhysCellId, cgi-Info SEQUENCE{ cellGlobalId CellGlobalIdEUTRA, trackingAreaCode TrackingAreaCode,plmn-IdentityList PLMN-IdentityList2 OPTIONAL } OPTIONAL, measResultSEQUENCE { rsrpResult RSRP-Range OPTIONAL, rsrqResult RSRQ-RangeOPTIONAL, ..., [[ additionalSI-Info-r9 AdditionalSI-Info-r9 OPTIONAL ]]} } MeasResultServFreqList-r10 ::= SEQUENCE (SIZE (1..maxServCell-r10))OF MeasResultServFreq-r10 MeasResultServFreq-r10 ::= SEQUENCE {servFreqId-r10 ServCellIndex-r10, measResultSCell-r10 SEQUENCE {rsrpResultSCell-r10 RSRP-Range, rsrqResultSCell-r10 RSRQ-Range }OPTIONAL, measResultBestNeighCell-r10 SEQUENCE { physCellId-r10PhysCellId, rsrpResultNCell-r10 RSRP-Range, rsrqResultNCell-r10RSRQ-Range } OPTIONAL, ... } MeasResultListUTRA ::= SEQUENCE (SIZE(1..maxCellReport)) OF MeasResultUTRA MeasResultUTRA ::= SEQUENCE {physCellId CHOICE { fdd PhysCellIdUTRA-FDD, tdd PhysCellIdUTRA-TDD },cgi-Info SEQUENCE { cellGlobalId CellGlobalIdUTRA, locationAreaCode BITSTRING (SIZE (16)) OPTIONAL, routingAreaCode BIT STRING (SIZE (8))OPTIONAL, plmn-IdentityList PLMN-IdentityList2 OPTIONAL } OPTIONAL,measResult SEQUENCE { utra-RSCP INTEGER (−5..91) OPTIONAL, utra-EcN0INTEGER (0..49) OPTIONAL, ..., [[ additionalSI-Info-r9AdditionalSI-Info-r9 OPTIONAL ]] } } MeasResultListGERAN ::= SEQUENCE(SIZE (1..maxCellReport)) OF MeasResultGERAN MeasResultGERAN ::=SEQUENCE { carrierFreq CarrierFreqGERAN, physCellId PhysCellIdGERAN,cgi-Info SEQUENCE { cellGlobalId CellGlobalIdGERAN, routingAreaCode BITSTRING (SIZE (8)) OPTIONAL } OPTIONAL, measResult SEQUENCE { rssiINTEGER (0..63), ... } } MeasResultsCDMA2000 ::= SEQUENCE {preRegistrationStatusHRPD BOOLEAN, measResultListCDMA2000MeasResultListCDMA2000 } MeasResultListCDMA2000 ::= SEQUENCE (SIZE(1..maxCellReport)) OF MeasResultCDMA2000 MeasResultCDMA2000 ::=SEQUENCE { physCellId PhysCellIdCDMA2000, cgi-Info CellGlobalIdCDMA2000OPTIONAL, measResult SEQUENCE { pilotPnPhase INTEGER  (0..32767)OPTIONAL, pilotStrength INTEGER (0..63), ... } } MeasResultForECID-r9::= SEQUENCE { ue-RxTxTimeDiffResult-r9 INTEGER (0..4095), currentSFN-r9BIT STRING (SIZE (10)) } PLMN-IdentityList2 ::= SEQUENCE (SIZE (1..5))OF PLMN-Identity AdditionalSI-Info-r9 ::= SEQUENCE { csg-MemberStatus-r9ENUMERATED {member} OPTIONAL, csg-Identity-r9 CSG-Identity OPTIONAL } --ASN1STOP

In some demonstrative embodiments, the measurement information receivedfrom UE 102 may be used by the cellular network, e.g., by node 104and/or any other element of the cellular network, with respect toassisting making and/or controlling WLAN mobility decisions, fullynetwork controlled mobility and/or UE controlled mobility with networkassistance, as described below.

In some demonstrative embodiments, node 104 may trigger a UE, e.g., UE102 and/or another UE, to start or stop offloading to WLAN 107, forexample, based on the measurement information corresponding to WLAN 107and/or based on any other information, e.g., as described below.

In some demonstrative embodiments, UE 102 may receive from node 104 atleast one trigger message, e.g., via the cellular link between UE 102and node 104, and controller 145 may control access network selection ofUE 102 based on the trigger message, e.g., as described below.

In some demonstrative embodiments, node 104 may receive one or moremeasurement reports from UE 102 and/or one or more other UEs, and, basedon the measurement reports, node 104 may request a UE, e.g., UE 102, tomove one or more bearers to or from a WLAN, e.g., WLAN 107, and/or node104 may direct the UE to move one or more selected flows, e.g.,identified through QCI description or in any other manner, to a cellularnetwork, e.g., cell 103. Alternatively, node 104 may request UE 102 tomove all traffic to or from the WLAN.

In one example, a node, e.g., node 104, may schedule WLAN measurementsfor one or more WLAN capable UEs, e.g., UE 102, connected to the node. AUE may perform WLAN measurements, e.g., based on a configuration definedby the node, and the UE may report results of the measurements to thenode. The node may trigger the UE to start (or stop) offload to a WLAN.The UE may decide to trigger the offload based, for example, on WLANand/or cellular network load, WLAN and/or cellular radio conditions,and/or one or more other parameters, e.g., as described below.

In some demonstrative embodiments, node 104 may use RRC signaling torequest, assist, control and/or cause UE 102 to switch between thecellular and non-cellular networks.

In some demonstrative embodiments, node 104 may trigger the accessnetwork selection by UE 102 by transmitting a trigger message to UE 102.

In some demonstrative embodiments, node 104 may transmit the triggermessage directly to UE 102, e.g., using a dedicated RRC signalingmessage, as described below.

For example, node 104 may trigger UE 102 to start or stop WLAN offload,for example, by transmitting to UE 102 a dedicated DLInformationTransferRRC message, a dedicated RRCConnectionReconfiguration RRC message, e.g.,with a MobilityControllnfo information element, a dedicatedHandoverFromEUTRAPreparationRequest RRC message, a dedicatedMobilityFromEUTRACommand RRC message, a dedicated RRCConnectionReleaseRRC message, a dedicated RRCConnectionReject message, and/or any otherRRC message.

In some demonstrative embodiments, node 104 may utilize a priority basedcell reselection mechanism configured to support WLAN, e.g., in additionto cellular networks.

In some demonstrative embodiments, the trigger message may include areselection frequency list including a plurality of WLAN frequencies,including a WLAN frequency of WLAN 107, associated with a plurality ofcell reselection priorities, including a reselection priority of WLAN107, e.g., as described below.

In some demonstrative embodiments, a System Information Block (SIB), forexample, SIB type 3, 5, 6, 7, 8 or a new SIB, may be configured toinclude frequency and/or priority information to support the prioritybased cell reselection mechanism for the WLAN. For example, node 104 maybroadcast the SIB including the reselection frequency list.

In some demonstrative embodiments, a RRCConnectionRelease message may beconfigured to include inter-RAT frequency and priority information forcell reselection, including WLAN network, frequency and priorityinformation.

In some demonstrative embodiments, node 104 may provide to UE 102 thereselection frequency list, e.g., as part of system information, whichmay be included in the RRCConnectionRelease message.

In some demonstrative embodiments, UE 102 may select a frequency withhighest priority that satisfies a cell selection criteria, e.g., when UE102 is at idle mode.

In one example, UE 102 may consider selecting to switch from a currentRAT cell, e.g., cell 103, to WLAN 107, for example, if the WLAN prioritydefined for WLAN 107 is greater than a priority of the current RAT, forexample, according to the cell reselection criteria, e.g., when UE 102determines a quality of the current cell is not good enough for UE 102.

In one example, the RRCConnectionRelease message may include thefrequency reselection list, e.g., as follows:

-- ASN1START RRCConnectionRelease ::= SEQUENCE {rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensionsCHOICE { cl CHOICE { rrcConnectionRelease-r8RRCConnectionRelease-r8-IEs, spare3 NULL, spare2 NULL, spare1 NULL },criticalExtensionsFuture SEQUENCE { } } } RRCConnectionRelease-r8-IEs::= SEQUENCE { releaseCause ReleaseCause, redirectedCarrierInfoRedirectedCarrierInfo OPTIONAL, -- Need ON idleModeMobilityControlInfoIdleModeMobilityControlInfo OPTIONAL, -- Need OP nonCriticalExtensionRRCConnectionRelease-v890-IEs OPTIONAL -- Need OP }RRCConnectionRelease-v890-IEs ::= SEQUENCE { lateNonCriticalExtensionOCTET STRING (CONTAINING RRCConnectionRelease-v9e0-IEs) OPTIONAL, --Need OP nonCriticalExtension RRCConnectionRelease-v920-IEs OPTIONAL --Need OP } -- Late non critical extensions RRCConnectionRelease-v9e0-IEs::= SEQUENCE { redirectedCarrierInfo-v9e0 RedirectedCarrierInfo-v9e0OPTIONAL, -- Cond NoRedirect-r8 idleModeMobilityControlInfo-v9e0IdleModeMobilityControlInfo-v9e0 OPTIONAL, -- Cond IdleInfoEUTRAnonCriticalExtension SEQUENCE { } OPTIONAL -- Need OP } -- Regular noncritical extensions RRCConnectionRelease-v920-IEs ::= SEQUENCE {cellInfoList-r9 CHOICE { geran-r9 CellInfoListGERAN-r9, utra-FDD-r9CellInfoListUTRA-FDD-r9, utra-TDD-r9 CellInfoListUTRA-TDD-r9, ...,utra-TDD-r10 CellInfoListUTRA-TDD-r10 } OPTIONAL, -- Cond RedirectionnonCriticalExtension RRCConnectionRelease-v1020-IEs OPTIONAL -- Need OP} RRCConnectionRelease-v1020-IEs ::= SEQUENCE { extendedWaitTime-r10INTEGER (1..1800) OPTIONAL, -- Need ON nonCriticalExtensionRRCConnectionRelease-v1200-IEs OPTIONAL -- Need OP }RRCConnectionRelease-v1200-IEs ::= SEQUENCE {idleModeMobilityControlInfo-v1200 IdleModeMobilityControlInfo-v1200OPTIONAL, -- Need OP nonCriticalExtension SEQUENCE { } OPTIONAL -- NeedOP } IdleModeMobilityControlInfo-v1200 ::= SEQUENCE {channelPriorityListWLAN ChannelPriorityListWLAN OPTIONAL, -- Need ON }ChannelPriorityListWLAN ::= SEQUENCE (SIZE (1..maxWLAN-Channel)) OFChannelPriorityWLAN ChannelPriorityWLAN ::= SEQUENCE { channelWLANChannel, cellReselectionPriority CellReselectionPriority }ReleaseCause ::= ENUMERATED {loadBalancingTAUrequired, other,cs-FallbackHighPriority-v1020, spare1} RedirectedCarrierInfo ::= CHOICE{ eutra ARFCN-ValueEUTRA, geran CarrierFreqsGERAN, utra-FDDARFCN-ValueUTRA, utra-TDD ARFCN-ValueUTRA, cdma2000-HRPDCarrierFreqCDMA2000, cdma2000-1xRTT CarrierFreqCDMA2000, ...,utra-TDD-r10 CarrierFreqListUTRA-TDD-r10 } RedirectedCarrierInfo-v9e0::= SEQUENCE { eutra-v9e0 ARFCN-ValueEUTRA-v9e0 }CarrierFreqListUTRA-TDD-r10 ::= SEQUENCE (SIZE (1..maxFreqUTRA-TDD-r10))OF ARFCN- ValueUTRA IdleModeMobilityControlInfo ::= SEQUENCE {freqPriorityListEUTRA FreqPriorityListEUTRA OPTIONAL, -- Need ONfreqPriorityListGERAN FreqsPriorityListGERAN OPTIONAL, -- Need ONfreqPriorityListUTRA-FDD FreqPriorityListUTRA-FDD OPTIONAL, -- Need ONfreqPriorityListUTRA-TDD FreqPriorityListUTRA-TDD OPTIONAL, -- Need ONbandClassPriorityListHRPD BandClassPriorityListHRPD OPTIONAL, -- Need ONbandClassPriorityList1XRTT BandClassPriorityList1XRTT OPTIONAL, -- NeedON t320 ENUMERATED { min5, min10, min20, min30, min60, min120, min180,spare1} OPTIONAL, -- Need OR ... } IdleModeMobilityControlInfo-v9e0 ::=SEQUENCE { freqPriorityListEUTRA-v9e0 SEQUENCE (SIZE (1..maxFreq)) OFFreqPriorityEUTRA-v9e0 } FreqPriorityListEUTRA ::= SEQUENCE (SIZE(1..maxFreq)) OF FreqPriorityEUTRA FreqPriorityEUTRA ::= SEQUENCE {carrierFreq ARFCN-ValueEUTRA, cellReselectionPriorityCellReselectionPriority } FreqPriorityEUTRA-v9e0 ::= SEQUENCE {carrierFreq-v9e0 ARFCN-ValueEUTRA-v9e0 OPTIONAL -- Cond EARFCN-max }FreqsPriorityListGERAN ::= SEQUENCE (SIZE (1..maxGNFG)) OFFreqsPriorityGERAN FreqsPriorityGERAN ::= SEQUENCE { carrierFreqsCarrierFreqsGERAN, cellReselectionPriority CellReselectionPriority }FreqPriorityListUTRA-FDD ::= SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OFFreqPriorityUTRA-FDD FreqPriorityUTRA-FDD ::= SEQUENCE { carrierFreqARFCN-ValueUTRA, cellReselectionPriority CellReselectionPriority }FreqPriorityListUTRA-TDD ::= SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OFFreqPriorityUTRA-TDD FreqPriorityUTRA-TDD ::= SEQUENCE { carrierFreqARFCN-ValueUTRA, cellReselectionPriority CellReselectionPriority }BandClassPriorityListHRPD ::= SEQUENCE (SIZE (1..maxCDMA-BandClass)) OFBandClassPriorityHRPD BandClassPriorityHRPD ::= SEQUENCE { bandClassBandclassCDMA2000, cellReselectionPriority CellReselectionPriority }BandClassPriorityList1XRTT ::= SEQUENCE (SIZE (1..maxCDMA-BandClass)) OFBandClassPriority1XRTT BandClassPriority1XRTT ::= SEQUENCE { bandClassBandclassCDMA2000, cellReselectionPriority CellReselectionPriority }CellInfoListGERAN-r9 ::= SEQUENCE (SIZE (1..maxCellInfoGERAN-r9)) OFCellInfoGERAN-r9 CellInfoGERAN-r9 ::= SEQUENCE { physCellId-r9PhysCellIdGERAN, carrierFreq-r9 CarrierFreqGERAN, systemInformation-r9SystemInfoListGERAN } CellInfoListUTRA-FDD-r9 ::= SEQUENCE (SIZE(1..maxCellInfoUTRA-r9)) OF CellInfoUTRA-FDD-r9 CellInfoUTRA-FDD-r9 ::=SEQUENCE { physCellId-r9 PhysCellIdUTRA-FDD, utra-BCCH-Container-r9OCTET STRING } CellInfoListUTRA-TDD-r9 ::= SEQUENCE (SIZE(1..maxCellInfoUTRA-r9)) OF CellInfoUTRA-TDD-r9 CellInfoUTRA-TDD-r9 ::=SEQUENCE { physCellId-r9 PhysCellIdUTRA-TDD, utra-BCCH-Container-r9OCTET STRING } CellInfoListUTRA-TDD-r10 ::= SEQUENCE (SIZE(1..maxCellInfoUTRA-r9)) OF CellInfoUTRA-TDD-r10 CellInfoUTRA-TDD-r10::= SEQUENCE { physCellId-r10 PhysCellIdUTRA-TDD, carrierFreq-r10ARFCN-ValueUTRA, utra-BCCH-Container-r10 OCTET STRING } -- ASN1STOP

In some demonstrative embodiments, the WLANChannel IE may define theWLAN channel, for example, by including a list of one or more WLANchannels. In one example, the WLANChannel IE may define the WLAN channelusing one or more WiFi channel identifiers, for example, wc1 may denotea first WiFi channel frequency, e.g., 2412 MHz, wc11 may denote aneleventh WiFi channel frequency, e.g., 2462 MHz, as follows:

-- ASN1START WLANChannel ::= ENUMERATED { wc1, wc2, wc3, wc4, wc5, wc6,wc7, wc8, wc9, wc10, wc11, wc12, wc13, wc14, wc131, wc132, wc132, wc133,wc133, wc134, wc134, wc135, wc136, wc136, wc137, wc137, wc138, wc138,wc183, wc184, wc185, wc187, wc188, wc189, wc192, wc196, wc7, wc8, wc9,wc11, wc12, wc16, wc34, wc, wc36, wc38, wc40, wc42, wc44, wc46, wc48,wc52, wc56, wc60, wc64, wc100, wc104, wc108, wc112, wc116, wc120, wc124,wc128, wc132, wc136, wc140, wc149, wc153, wc157, wc161, wc165, ...} --ASN1STOP

In some demonstrative embodiments, node 104 may adjust access classbarring probabilities according to relative loads of one or more WLANAPs, e.g., AP 106. For example, if the relative load of neighboring WLANAPs is lesser than the load of node 104, then node 104 may increase theaccess class barring probabilities to ensure that fewer UEs will selectnode 104 and more UEs will select WLAN AP 106.

In some demonstrative embodiments, the trigger message may include anaccess barring indication to bar UE 102 from using the cellular linkwith node 104, for example, in order to cause UE 102 to use a WLAN link,or to bar UE 102 from using the WLAN link with WLAN 107, for example, inorder to cause UE 102 to use a cellular link, e.g., as described below.

In one example, controller 145 may be configured to control UE 102,e.g., when UE is at Idle mode, to use WLAN access, e.g., to WLAN 107,instead of cellular access, e.g., to cell 103, for example, when UE 102is access class barred.

In some demonstrative embodiments, WLAN AP 106 be configured to supportaccess class barring mechanisms similar to the barring mechanisms of thecellular system, e.g., as described above. For example, WLAN AP 106 maybe configured to transmit an access barring indication to bar UE 102from using the WLAN link with AP 106, for example, in order to cause UE102 to use a cellular link, or to bar UE 102 from using the cellularlink with node 104, for example, in order to cause UE 102 to use WLANlink.

In some demonstrative embodiments, node 104 may be able to determinenetwork assistance information corresponding to WLAN 107, for example,based on the measurement information received from UE 102, e.g., asdescribed below.

For example, controller 144 may determine network assistance informationcorresponding to WLAN 107 and/or one or more other WLANs, e.g., based onthe measurement information received from UE 102. According to thisexample, node 104 may transmit one or more messages, e.g., a broadcastmessage to be received by one or more UEs and/or a dedicated messageaddressed to a particular UE, including the network assistanceinformation.

In some demonstrative embodiments, node 104 may transmit a messageincluding the network assistance information.

In some demonstrative embodiments, a node of a serving cell, e.g., node104, may use the measurement reports received from one or more UEs toassess the quality of various neighboring WLAN links.

In one example, node 104 may broadcast one or more messages, e.g., RRCmessages, for example, to be received by one or more UEs within acoverage area of cell 103, e.g., UEs in the RRC Idle state and/or UEs inthe RRC Connected state.

In another example, node 104 may transmit a message including thenetwork assistance information directly to a UE within a coverage areaof cell 103, e.g., a UE in the RRC Connected state.

In some demonstrative embodiments, the network assistance informationmay include or may represent a cellular load, a WLAN load, cellularsignal strength thresholds used for mobility decisions, e.g. a RSRPthreshold, WLAN signal strength thresholds used for mobility decisions,e.g., a RSSI threshold, an offload preference indicator, a WLAN overloadindicator, WLAN cell-barring information, a Probability for WLAN networkselection, a Probability for WLAN network selection per QCI, and/or anyother assistance information to assist access network selection by UE102.

In some demonstrative embodiments, transmitting selection probabilitiesas assistance information may be used to allow for a more gracefultransition of traffic between RATs, for example, to avoid nearsimultaneous transition of traffic flows.

Additionally or alternatively to providing the network assistanceinformation corresponding to one or more WLANs, e.g., WLAN 107, in somedemonstrative embodiments node 104 may transmit, e.g., broadcast,cellular assistance information relevant to one or more cellularnetworks, e.g., cell 103. The cellular assistance information may, forexample, allow a UE, e.g., UE 102, to make network selection decisions,which may be based on network load considerations, e.g., in addition toor instead of based on signal strength measurements.

In some demonstrative embodiments, the cellular assistance informationmay include information that may be used instead of the loadinformation. For example, when cell 103 may be overloaded, node 104 mayuse an access class barring mechanism to control the number of UEsassociating with cell 103, e.g., as described above.

In some demonstrative embodiments, node 104 may choose to offload weakusers to WLAN links, e.g., provided the WLAN link can support theminimum QoS.

In some demonstrative embodiments, node 104 may control access to cell103, for example, using SNR/SINR thresholds that identify candidate“weak UEs” for offloading to WLAN, e.g., as described below.

In some demonstrative embodiments, node 104 may use some measurementreports directly for generating network assistance information. Forexample, node 104 may use WLAN overload indicators reported by the UEsto notify other UEs that a particular WLAN AP, e.g., AP 106, isoverloaded.

In some demonstrative embodiments, node 104 may aggregate BSS_Load_Inforeports from multiple UEs to determine relative loads across neighboringWLAN APs and/or at node 104.

In some demonstrative embodiments, node 104 may generate and broadcastprobabilities of WLAN and cellular network selection, e.g., based on therelative loads. UE 102 may use the probabilities to make networkselection decisions.

In some demonstrative embodiments, node 104 may broadcast assistanceinformation for UE 102 using additional or alternative rankings, whichmay account for quality of service classes, e.g., assistance informationmay be sent per QCI. This assistance information may be, for example, inthe form of per QCI probability of network selection across the cellularnetworks and/or WLANs. In one example, UE 102 may be able to make WLANQoS measurements on one or more particular quality of service classes,e.g., which may be mapped to 3GPP QCI, and UE 102 may report themeasurements back to node 104. Node 104 may, for example, receiveperiodic reports from UE 102 and/or other UEs. Node 104 may assign, forexample, probability of network selection per QCI, e.g., to result inselection of WLAN being blocked for Real-Time services, and allowed forbest effort.

In some demonstrative embodiments, node 104 may use UE reports on “otherdetected” WLAN cells, for example, to discover neighboring WLAN APsavailable for network selection. According to these embodiments, node104 may store this information regarding the neighboring WLAN APs. Node104 may assist UE 102 in scanning for a select group of WLAN APs, forexample, by providing WLAN network identifiers, channels, frequenciesand/or other information relevant to the neighbor WLAN networks, thussaving on scan time and battery power of UE 102.

In some demonstrative embodiments, UE 102 may be configured to providethe WLAN measurement information and/or to perform access networkselection, for example, when UE 102 is at the RRC Idle State.

For example, UE 102 may be in RRC Idle state “camped” on cell 103, whilehaving one or more active connections on neighboring WLAN cells, e.g.,WLAN 107. According to this example, UE 102 may use the networkselection assistance information broadcast by node 104, e.g., asdescribed above, to make RAT selection decisions. For example, node 104may assess WLAN link information and provide the network selectionassistance information, for example, based on WLAN measurementinformation from one or more other UEs, e.g., which may be associatedwith cell 103 or may at least have a partial set of bearers associatedwith the cellular link with node 104.

In some demonstrative embodiments, UE 102 may provide assistanceinformation (“UE assistance information”), which may assist the networkin making traffic steering decisions and/or provide improved “networkassistance” to UEs for making traffic steering decision. UE 102 mayprovide the UE assistance information, e.g., even when at the RRC IdleState, for example, through piggy-backing on a random access RACHprocedure, e.g., while performing location updates, or upon response topaging requests.

In some demonstrative embodiments, UE 102 use theRRCConnectionSetupRequest message with a Establishment Clause indicatingWLAN overload, WLAN-QoS-Unacceptable, and the like.

In some demonstrative embodiments, UE may use theRRCConnectionSetupComplete message to provide the WLAN relatedinformation.

FIG. 2 schematically illustrates a sequence diagram of communicatingWLAN measurement information and network selection of a UE 202 at an RRCConnected state with respect to a node 204, in accordance with somedemonstrative embodiments. In some demonstrative embodiments, UE 202 mayperform the functionality of UE 102 (FIG. 1) and/or node 204 may performthe functionality of node 104 (FIG. 1).

As indicated at box 210, in some demonstrative embodiments node 204 maybe aware of at least one WLAN AP 206, for example, based on reports fromone or more UEs and/or any other reporting and/or configurationmechanism.

In some demonstrative embodiments, node 204 may transmit an RRC message212, e.g., a RRCConnectionReconfiguration message including themeasConfig IE, including configuration information to configure WLANmeasurements to be performed by UE 202 with respect to WLAN AP 206,e.g., as described above.

In some demonstrative embodiments, UE 202 may receive WLAN information,e.g., BSS Load information 214, from WLAN AP 206.

As indicated at box 216, in some demonstrative embodiments UE 202 may beassociated with one or more WLAN links and/or communicate one or moretraffic flows with WLAN AP 206.

As indicated by box 218, in some demonstrative embodiments UE 202 mayperform WLAN measurements corresponding to WLAN AP 206, for example,based on the configuration information of RRC message 212, e.g., asdescribed above.

In some demonstrative embodiments, UE 202 may transmit to node 204 areport message 220 including the WLAN measurement report, e.g., asdescribed above.

In some demonstrative embodiments, report message 220 may optionallyinclude any additional UE assistance information, e.g., including anindication that UE 202 prefers to use WLAN AP 206.

As indicated by box 222, in some demonstrative embodiments node 204 maymake one or more network selection decisions with respect to UE 202, forexample, based on the WLAN measurement information received from UE 202and/or one or more other UEs, and/or based on load and/or qualityinformation corresponding to the cell of node 204, e.g., as describedabove.

In some demonstrative embodiments, node 204 may transmit an RRC message224 to trigger UE 202 to establish a connection or release a connectionto a network, for example, to WLAN AP 206, e.g., as described above.

As indicated at box 226, in some demonstrative embodiments UE 202 mayestablish the connection or release the connection to the network basedone the message 224, e.g., as described above.

FIG. 3 schematically illustrates a sequence diagram of communicatingWLAN measurement information and network selection of a UE 302 at an RRCIdle state with respect to a node 304, in accordance with somedemonstrative embodiments. In some demonstrative embodiments, UE 302 mayperform the functionality of UE 102 (FIG. 1) and/or node 304 may performthe functionality of node 104 (FIG. 1).

In some demonstrative embodiments, UE 302 may receive WLAN information,e.g., BSS Load information 310, from at least one WLAN AP 306.

As indicated at box 312, in some demonstrative embodiments UE 302 may beassociated with one or more WLAN links and/or communicate one or moretraffic flows with WLAN AP 306.

In some demonstrative embodiments, node 304 may configure measurementsat UE 302, for example, when UE 302 is initially connects to thecellular network. For example, a RRC message 314, e.g., aRRCConnectionReconfiguration message, may be transmitted by node 304,and may include configuration information to configure WLAN measurementsto be performed by UEs with respect to WLAN AP 306, e.g., as describedabove. For example, UE 302 may continue to provide the measurementreports, e.g., periodically, for example, even while UE 302 is in Idlestate. For example, UE 302 may provide the measurement reports bypiggy-back measurements with location updates and/or paging responses,which may force UE 302 to move to the connected state. As indicated bybox 316, in some demonstrative embodiments UE 302 may perform WLANmeasurements corresponding to WLAN AP 306, e.g., as described above.

In some demonstrative embodiments, UE 302 may switch to the connectedstate, e.g., by performing a location update and/or any other procedure.

In some demonstrative embodiments, UE 302 may transmit to node 304 areport message 318 including the WLAN measurement report, e.g., asdescribed above.

In some demonstrative embodiments, report message 318 may optionallyinclude UE assistance information, e.g., including an indication that UE302 prefers to use WLAN AP 306.

In some demonstrative embodiments node 304 may make one or more networkselection decisions with respect to UE 302, for example, based on theWLAN measurement information received from UE 302 and/or one or moreother UEs, and/or based on load and/or quality information correspondingto the cell of node 304, e.g., as described above.

In some demonstrative embodiments, node 304 may broadcast one or moremessages 320 to assist access network selection by UE 302, e.g., asdescribed above.

As indicated at box 322, in some demonstrative embodiments UE 302 selectto move one or more flows to node 304, for example, based on messages320 and/or one or more parameters of WLAN AP 306, e.g., as describedabove.

In some demonstrative embodiments, UE 302 may send a connection requestto connect to node 304.

FIG. 4 schematically illustrates a sequence diagram of communicatingnetwork selection assistance information between a node 404 and a UE402, in accordance with some demonstrative embodiments. In somedemonstrative embodiments, UE 402 may perform the functionality of UE102 (FIG. 1) and/or node 404 may perform the functionality of node 104(FIG. 1).

As indicated at box 410, in some demonstrative embodiments UE 402 may beeither at the RRC Idle state or the RRC Connected State with respect tonode 404.

As indicated at box 412, node 404 may determine one or more parameterscorresponding to a WLAN AP 406, for example, based on WLAN measurementinformation received from one or more UEs, and/or based on load and/orquality information corresponding to the cell of node 404, e.g., asdescribed above.

In some demonstrative embodiments, node 404 may transmit one or moremessages 414 to assist access network selection by UE 402, e.g., asdescribed above.

As indicated at box 416, in some demonstrative embodiments UE 404 maymake a network selection decision, for example, based on messages 320,e.g., as described above.

In some demonstrative embodiments, UE 402 may send a connection requestto connect to node 404, e.g., if UE 402 selects to connect to node 404.

In some demonstrative embodiments, UE 402 may send a connection requestto connect to WLAN AP 420, e.g., if UE 402 selects to connect to WLAN AP406.

Reference is made to FIG. 5, which schematically illustrates a method ofnetwork selection, in accordance with some demonstrative embodiments. Insome embodiments, one or more of the operations of the method of FIG. 5may be performed by a wireless communication system e.g., system 100(FIG. 1); a wireless communication device, e.g., UE 102 (FIG. 1), node104 (FIG. 1) and/or AP 106 (FIG. 1); and/or a wireless communicationunit, e.g., wireless communication units 110 and/or 130 (FIG. 1).

As indicated at block 502, the method may include communicating betweena cellular node and a wireless communication device at least oneconfiguration message to configure one or more measurements to beperformed by the wireless communication device with respect to at leastone WLAN. For example, node 104 (FIG. 1) may transmit the configurationmessage to UE 102 (FIG. 1), e.g., as described above.

As indicated at block 504, the method may include communicating betweenthe wireless communication device and the cellular node at least onereport message including measurement information corresponding to theWLAN. For example, UE 102 (FIG. 1) may transmit the report message to104 (FIG. 1), e.g., as described above.

As indicated at block 506, the method may include triggering thewireless communication device to start or stop offloading to the WLAN.For example, node 104 (FIG. 1) may transmit a message to trigger UE 102(FIG. 1) to start or stop offloading to WLAN AP 106 (FIG. 1), e.g., asdescribed above.

As indicated at block 508, the method may include communicating networkassistance information corresponding to the WLAN between the cellularnode and the wireless communication device. For example, node 104(FIG. 1) may transmit a message including the network assistanceinformation corresponding to WLAN AP 106 (FIG. 1), e.g., as describedabove.

Reference is made to FIG. 6, which schematically illustrates a productof manufacture 300, in accordance with some demonstrative embodiments.Product 600 may include a non-transitory machine-readable storage medium602 to store logic 604, which may be used, for example, to perform atleast part of the functionality of UE 102 (FIG. 1), node 104 (FIG. 1),AP 106 (FIG. 1), wireless communication unit 110 (FIG. 1), wirelesscommunication unit 130 (FIG. 1) to perform one or more operations of theprocedures of FIGS. 2, 3 and/or 4, and/or to perform one or moreoperations of the method of FIG. 5. The phrase “non-transitorymachine-readable medium” is directed to include all computer-readablemedia, with the sole exception being a transitory propagating signal.

In some demonstrative embodiments, product 600 and/or machine-readablestorage medium 602 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 602 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 604 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 604 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

Examples

The following examples pertain to further embodiments.

Example 1 includes a cellular node comprising a radio to transmit to aUser Equipment (UE) at least one configuration message to configure oneor more measurements to be performed by the UE with respect at least oneWireless Local Area Network (WLAN), and to receive from the UE at leastone report message including measurement information corresponding tothe WLAN.

Example 2 includes the subject matter of Example 1, and optionally,wherein the configuration message comprises at least one parameterselected from the group consisting of at least one identifier of the atleast one WLAN, at least one frequency band of the at least one WLAN,and at least one frequency channel of the at least one WLAN.

Example 3 includes the subject matter of Example 2, and optionally,wherein the at least one identifier comprises at least one identifierselected from the group consisting of a Service Set Identification(SSID), an Extended SSID (ESSID), a Basic SSID (SSID), a RoamingConsortium, a Hotspot Operator Friendly Name, a Network AccessIdentifier (NAI) Home Realm, and a Mobility Domain.

Example 4 includes the subject matter of Example 2 or 3, and optionally,wherein the configuration message comprises a Measurement InformationElement (IE) including the at least one parameter.

Example 5 includes the subject matter of any one of Examples 1-4, andoptionally, wherein the configuration message comprises reportingconfiguration information defining at least one configuration selectedfrom the group consisting of a reporting criterion defining a criterionto trigger the UE to send the report message, and a reporting formatdefining the measurement information.

Example 6 includes the subject matter of Example 5, and optionally,wherein the reporting criterion comprises a criterion related to atleast one parameter selected from the group consisting of a ReceivedSignal Strength Indicator (RSSI) threshold, a Received Channel PowerIndicator (RCPI) threshold, a Received Power Indicator (RPI) threshold,a Received Signal to Noise Indicator (RSNI) threshold, and a WLANchannel utilization.

Example 7 includes the subject matter of any one of Examples 1-6, andoptionally, wherein the configuration message comprises a Radio-ResourceControl (RRC) signaling message.

Example 8 includes the subject matter of Example 7, and optionally,wherein the RRC signaling message comprises aRRCConnectionReconfiguration message.

Example 9 includes the subject matter of any one of Examples 1-8, andoptionally, wherein the report message comprises at least one parameterselected from the group consisting of an identifier of the WLAN, achannel of the WLAN, a privacy parameter of the WLAN, a securityparameter of the WLAN, a Received Signal Strength Indicator (RSSI) ofthe WLAN, a Received Channel Power Indicator (RCPI) of the WLAN, aReceived Power Indicator (RPI) of the WLAN, a Received Signal to NoiseIndicator (RSNI) threshold of the WLAN, a connection Quality of Service(QoS) of the WLAN, a load parameter indicating a load of the WLAN, andan indication of one or more other WLANs detected by the UE.

Example 10 includes the subject matter of any one of Examples 1-9, andoptionally, wherein the report message comprises a Radio-ResourceControl (RRC) signaling message.

Example 11 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the cellular node is to receive the report messagewhen the UE is at a Radio-Resource Control (RRC) idle state.

Example 12 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the cellular node is to receive the report messagewhen the UE is at a Radio-Resource Control (RRC) connected state.

Example 13 includes the subject matter of any one of Examples 1-12 andoptionally comprising a controller to determine network assistanceinformation corresponding to the at least one WLAN based on themeasurement information, wherein the radio is to transmit a messageincluding the network assistance information.

Example 14 includes the subject matter of Example 13, and optionally,wherein the radio is to broadcast the message including the networkassistance information.

Example 15 includes the subject matter of Example 13, and optionally,wherein the radio is to transmit to another UE a dedicated messageincluding the network assistance information.

Example 16 includes the subject matter of any one of Examples 13-15, andoptionally, wherein the network assistance information represents a loador a quality of service of the WLAN.

Example 17 includes the subject matter of any one of Examples 1-12, andoptionally, wherein the radio is to transmit a message to trigger the UEto start or stop offloading to the WLAN.

Example 18 includes the subject matter of Example 17, and optionally,wherein the radio is to transmit to the UE at least one control messageincluding a predefined trigger to trigger the UE to start or stopoffloading to the WLAN.

Example 19 includes the subject matter of Example 18, and optionally,wherein the control message comprises a Radio-Resource Control (RRC)signaling message.

Example 20 includes the subject matter of Example 19, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 21 includes the subject matter of any one of Examples 1-12, andoptionally, wherein the radio is to transmit a message including areselection frequency list including a plurality of WLAN frequenciesassociated with a plurality of cell reselection priorities, the WLANfrequencies including a WLAN frequency of the WLAN and a reselectionpriority of the WLAN is based on the measurement information.

Example 22 includes the subject matter of any one of Examples 1-12, andoptionally, wherein, based on the measurement information the radio isto transmit a message including an access barring indication to bar theUE from using a cellular link with the cellular node.

Example 23 includes the subject matter of any one of Examples 1-22 andoptionally comprising an Evolved Node B (eNB).

Example 24 includes a User Equipment (UE) comprising a Wireless LocalArea Network (WLAN) transceiver; a cellular transceiver to receive froma cellular node at least one trigger message; and a controller tocontrol access network selection of the UE with respect to a WLAN basedon the trigger message.

Example 25 includes the subject matter of Example 24, and optionally,wherein the trigger message comprises a Radio-Resource Control (RRC)signaling message.

Example 26 includes the subject matter of Example 25, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 27 includes the subject matter of Example 24, and optionally,wherein the trigger message includes a reselection frequency listincluding a plurality of WLAN frequencies associated with a plurality ofcell reselection priorities.

Example 28 includes the subject matter of Example 24, and optionally,wherein the trigger message comprises an access barring indication tobar the UE from using a cellular link with the cellular node, andwherein, in response to the access barring indication, the controller isto control the WLAN transceiver to connect to the WLAN.

Example 29 includes a cellular node comprising:

a radio to transmit to a User Equipment (UE) at least one Radio-ResourceControl (RRC) signaling message including an offload trigger to triggerthe UE to start or stop offloading to a WLAN.

Example 30 includes the subject matter of Example 29, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 31 includes the subject matter of Example 29 or 30 andoptionally comprising a controller to control the radio to transmit theRRC message based on measurement information corresponding to the WLAN.

Example 32 includes the subject matter of Example 31, and optionally,wherein the radio is to receive the measurement information from the UE.

Example 33 includes the subject matter of Example 31, and optionally,wherein the radio is to receive the measurement information from anotherUE.

Example 34 includes the subject matter of any one of Examples 29-33 andoptionally comprising an Evolved Node B (eNB).

Example 35 includes a cellular node comprising a radio to transmit amessage including a reselection frequency list including a plurality ofWireless Local Are Network (WLAN) frequencies of one or more WLANS, anda plurality of cell reselection priorities prioritizing the WLANfrequencies.

Example 36 includes the subject matter of Example 35 and optionallycomprising a controller to control the radio to transmit the messagebased on measurement information corresponding to the WLANs.

Example 37 includes the subject matter of Example 36, and optionally,wherein the radio is to receive the measurement information from a UE,and to transmit the message to the UE.

Example 38 includes the subject matter of Example 36, and optionally,wherein the radio is to transmit the message to a UE, and to receive themeasurement information from another UE.

Example 39 includes the subject matter of any one of Examples 35-38, andoptionally, wherein the message comprises a Radio-Resource Control (RRC)signaling message.

Example 40 includes the subject matter of Example 39, and optionally,wherein the RRC signaling message comprises a RRCConnectionReleasemessage.

Example 41 includes the subject matter of any one of Examples 35-40 andoptionally comprising an Evolved Node B (eNB).

Example 42 includes a method comprising communicating between a cellularnode and a User Equipment (UE) at least one configuration message toconfigure one or more measurements to be performed by the UE withrespect at least one Wireless Local Area Network (WLAN); andcommunicating between the UE and the cellular node at least one reportmessage including measurement information corresponding to the WLAN.

Example 43 includes the subject matter of Example 42, and optionally,wherein the configuration message comprises at least one parameterselected from the group consisting of at least one identifier of the atleast one WLAN, at least one frequency band of the at least one WLAN,and at least one frequency channel of the at least one WLAN.

Example 44 includes the subject matter of Example 43, and optionally,wherein the at least one identifier comprises at least one identifierselected from the group consisting of a Service Set Identification(SSID), an Extended SSID (ESSID), a Basic SSID (SSID), a RoamingConsortium, a Hotspot Operator Friendly Name, a Network AccessIdentifier (NAI) Home Realm, and a Mobility Domain.

Example 45 includes the subject matter of Example 43 or 44, andoptionally, wherein the configuration message comprises a MeasurementInformation Element (IE) including the at least one parameter.

Example 46 includes the subject matter of any one of Examples 42-45, andoptionally, wherein the configuration message comprises reportingconfiguration information defining at least one configuration selectedfrom the group consisting of a reporting criterion defining a criterionto trigger the UE to send the report message, and a reporting formatdefining the measurement information.

Example 47 includes the subject matter of Example 46, and optionally,wherein the reporting criterion comprises a criterion related to atleast one parameter selected from the group consisting of a ReceivedSignal Strength Indicator (RSSI) threshold, a Received Channel PowerIndicator (RCPI) threshold, a Received Power Indicator (RPI) threshold,a Received Signal to Noise Indicator (RSNI) threshold, and a WLANchannel utilization.

Example 48 includes the subject matter of any one of Examples 42-47, andoptionally, wherein the configuration message comprises a Radio-ResourceControl (RRC) signaling message.

Example 49 includes the subject matter of Example 48, and optionally,wherein the RRC signaling message comprises aRRCConnectionReconfiguration message.

Example 50 includes the subject matter of any one of Examples 42-49, andoptionally, wherein the report message comprises at least one parameterselected from the group consisting of an identifier of the WLAN, achannel of the WLAN, a privacy parameter of the WLAN, a securityparameter of the WLAN, a Received Signal Strength Indicator (RSSI) ofthe WLAN, a Received Channel Power Indicator (RCPI) of the WLAN, a

Received Power Indicator (RPI) of the WLAN, a Received Signal to NoiseIndicator (RSNI) threshold of the WLAN, a connection Quality of Service(QoS) of the WLAN, a load parameter indicating a load of the WLAN, andan indication of one or more other WLANs detected by the UE.

Example 51 includes the subject matter of any one of Examples 42-50, andoptionally, wherein the report message comprises a Radio-ResourceControl (RRC) signaling message.

Example 52 includes the subject matter of any one of Examples 42-51 andoptionally comprising communicating the report message when the UE is ata Radio-Resource Control (RRC) idle state.

Example 53 includes the subject matter of any one of Examples 42-51 andoptionally comprising communicating the report message when the UE is ata Radio-Resource Control (RRC) connected state.

Example 54 includes the subject matter of any one of Examples 42-53 andoptionally comprising determining network assistance informationcorresponding to the at least one WLAN based on the measurementinformation, and transmitting a message including the network assistanceinformation.

Example 55 includes the subject matter of Example 54 and optionallycomprising broadcasting the message including the network assistanceinformation.

Example 56 includes the subject matter of Example 54 and optionallycomprising transmitting to another UE a dedicated message including thenetwork assistance information.

Example 57 includes the subject matter of any one of Examples 54-56, andoptionally, wherein the network assistance information represents a loador a quality of service of the WLAN.

Example 58 includes the subject matter of any one of Examples 42-53 andoptionally comprising communicating between the cellular node and the UEa message to trigger the UE to start or stop offloading to the WLAN.

Example 59 includes the subject matter of Example 58 and optionallycomprising communicating between the cellular node and the UE at leastone control message including a predefined trigger to trigger the UE tostart or stop offloading to the WLAN.

Example 60 includes the subject matter of Example 59, and optionally,wherein the control message comprises a Radio-Resource Control (RRC)signaling message.

Example 61 includes the subject matter of Example 60, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 62 includes the subject matter of any one of Examples 42-53 andoptionally comprising transmitting a message including a reselectionfrequency list including a plurality of WLAN frequencies associated witha plurality of cell reselection priorities, the WLAN frequenciesincluding a WLAN frequency of the WLAN and a reselection priority of theWLAN is based on the measurement information.

Example 63 includes the subject matter of any one of Examples 42-53 andoptionally comprising, based on the measurement information,transmitting a message including an access barring indication to bar theUE from using a cellular link with the cellular node.

Example 64 includes the subject matter of any one of Examples 42-63, andoptionally, wherein the cellular node comprises an Evolved Node B (eNB).

Example 65 includes a method comprising receiving at a User Equipment(UE) at least one trigger message from a cellular node over a cellularlink; and controlling access network selection of the UE with respect toa Wireless Local Area Network (WLAN) based on the trigger message.

Example 66 includes the subject matter of Example 65, and optionally,wherein the trigger message comprises a Radio-Resource Control (RRC)signaling message.

Example 67 includes the subject matter of Example 66, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 68 includes the subject matter of Example 65, and optionally,wherein the trigger message includes a reselection frequency listincluding a plurality of WLAN frequencies associated with a plurality ofcell reselection priorities.

Example 69 includes the subject matter of Example 65, and optionally,wherein the trigger message comprises an access barring indication tobar the UE from using a cellular link with the cellular node, andwherein the method comprises, in response to the access barringindication, controlling the UE connect to the WLAN.

Example 70 includes a method comprising communicating between a cellularnode and a User Equipment (UE) at least one Radio-Resource Control (RRC)signaling message including an offload trigger to trigger the UE tostart or stop offloading to a WLAN.

Example 71 includes the subject matter of Example 70, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 72 includes the subject matter of Example 70 or 71 andoptionally comprising transmitting the RRC message based on measurementinformation corresponding to the WLAN.

Example 73 includes the subject matter of Example 72 and optionallycomprising receiving the measurement information from the UE.

Example 74 includes the subject matter of Example 72 and optionallycomprising receiving the measurement information from another UE.

Example 75 includes a method comprising transmitting from a cellularnode a message including a reselection frequency list including aplurality of Wireless Local Are Network (WLAN) frequencies of one ormore WLANS, and a plurality of cell reselection priorities prioritizingthe WLAN frequencies.

Example 76 includes the subject matter of Example 75 and optionallycomprising transmitting the message based on measurement informationcorresponding to the WLANs.

Example 77 includes the subject matter of Example 76 and optionallycomprising receiving the measurement information from a UE, andtransmitting the message to the UE.

Example 78 includes the subject matter of Example 76 and optionallycomprising transmitting the message to a UE and receiving themeasurement information from another UE.

Example 79 includes the subject matter of any one of Examples 75-78, andoptionally, wherein the message comprises a Radio-Resource Control (RRC)signaling message.

Example 80 includes the subject matter of Example 79, and optionally,wherein the RRC signaling message comprises a RRCConnectionReleasemessage.

Example 81 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in communicating between a cellular node and a User Equipment(UE) at least one configuration message to configure one or moremeasurements to be performed by the UE with respect at least oneWireless Local Area Network (WLAN); and communicating between the UE andthe cellular node at least one report message including measurementinformation corresponding to the WLAN.

Example 82 includes the subject matter of Example 89, and optionally,wherein the configuration message comprises at least one parameterselected from the group consisting of at least one identifier of the atleast one WLAN, at least one frequency band of the at least one WLAN,and at least one frequency channel of the at least one WLAN.

Example 83 includes the subject matter of Example 82, and optionally,wherein the at least one identifier comprises at least one identifierselected from the group consisting of a Service Set Identification(SSID), an Extended SSID (ESSID), a Basic SSID (SSID), a RoamingConsortium, a Hotspot Operator Friendly Name, a Network AccessIdentifier (NAI) Home Realm, and a Mobility Domain.

Example 84 includes the subject matter of Example 82 or 83, andoptionally, wherein the configuration message comprises a MeasurementInformation Element (IE) including the at least one parameter.

Example 85 includes the subject matter of any one of Examples 81-84, andoptionally, wherein the configuration message comprises reportingconfiguration information defining at least one configuration selectedfrom the group consisting of a reporting criterion defining a criterionto trigger the UE to send the report message, and a reporting formatdefining the measurement information.

Example 86 includes the subject matter of Example 85, and optionally,wherein the reporting criterion comprises a criterion related to atleast one parameter selected from the group consisting of a ReceivedSignal Strength Indicator (RSSI) threshold, a Received Channel PowerIndicator (RCPI) threshold, a Received Power Indicator (RPI) threshold,a Received Signal to Noise Indicator (RSNI) threshold, and a WLANchannel utilization.

Example 87 includes the subject matter of any one of Examples 81-86, andoptionally, wherein the configuration message comprises a Radio-ResourceControl (RRC) signaling message.

Example 88 includes the subject matter of Example 87, and optionally,wherein the RRC signaling message comprises aRRCConnectionReconfiguration message.

Example 89 includes the subject matter of any one of Examples 81-88, andoptionally, wherein the report message comprises at least one parameterselected from the group consisting of an identifier of the WLAN, achannel of the WLAN, a privacy parameter of the WLAN, a securityparameter of the WLAN, a Received Signal Strength Indicator (RSSI) ofthe WLAN, a Received Channel Power Indicator (RCPI) of the WLAN, aReceived Power Indicator (RPI) of the WLAN, a Received Signal to NoiseIndicator (RSNI) threshold of the WLAN, a connection Quality of Service(QoS) of the WLAN, a load parameter indicating a load of the WLAN, andan indication of one or more other WLANs detected by the UE.

Example 90 includes the subject matter of any one of Examples 81-89, andoptionally, wherein the report message comprises a Radio-ResourceControl (RRC) signaling message.

Example 91 includes the subject matter of any one of Examples 81-90, andoptionally, wherein the instructions result in communicating the reportmessage when the UE is at a Radio-Resource Control (RRC) idle state.

Example 92 includes the subject matter of any one of Examples 81-90, andoptionally, wherein the instructions result in communicating the reportmessage when the UE is at a Radio-Resource Control (RRC) connectedstate.

Example 93 includes the subject matter of any one of Examples 81-92, andoptionally, wherein the instructions result in determining networkassistance information corresponding to the at least one WLAN based onthe measurement information, and transmitting a message including thenetwork assistance information.

Example 94 includes the subject matter of Example 93, and optionally,wherein the instructions result in broadcasting the message includingthe network assistance information.

Example 95 includes the subject matter of Example 93, and optionally,wherein the instructions result in transmitting to another UE adedicated message including the network assistance information.

Example 96 includes the subject matter of any one of Examples 93-95, andoptionally, wherein the network assistance information represents a loador a quality of service of the WLAN.

Example 97 includes the subject matter of any one of Examples 81-92, andoptionally, wherein the instructions result in communicating between thecellular node and the UE a message to trigger the UE to start or stopoffloading to the WLAN.

Example 98 includes the subject matter of Example 97, and optionally,wherein the instructions result in communicating between the cellularnode and the UE at least one control message including a predefinedtrigger to trigger the UE to start or stop offloading to the WLAN.

Example 99 includes the subject matter of Example 98, and optionally,wherein the control message comprises a Radio-Resource Control (RRC)signaling message.

Example 100 includes the subject matter of Example 99, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 101 includes the subject matter of any one of Examples 81-92,and optionally, wherein the instructions result in transmitting amessage including a reselection frequency list including a plurality ofWLAN frequencies associated with a plurality of cell reselectionpriorities, the WLAN frequencies including a WLAN frequency of the WLANand a reselection priority of the WLAN is based on the measurementinformation.

Example 102 includes the subject matter of any one of Examples 81-92,and optionally, wherein the instructions result in, based on themeasurement information, transmitting a message including an accessbarring indication to bar the UE from using a cellular link with thecellular node.

Example 103 includes the subject matter of any one of Examples 81-102,and optionally, wherein the cellular node comprises an Evolved Node B(eNB).

Example 104 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in receiving at a User Equipment (UE) at least one triggermessage from a cellular node over a cellular link; and controllingaccess network selection of the UE with respect to a Wireless Local AreaNetwork (WLAN) based on the trigger message.

Example 105 includes the subject matter of Example 104, and optionally,wherein the trigger message comprises a Radio-Resource Control (RRC)signaling message.

Example 106 includes the subject matter of Example 105, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 107 includes the subject matter of Example 104, and optionally,wherein the trigger message includes a reselection frequency listincluding a plurality of WLAN frequencies associated with a plurality ofcell reselection priorities.

Example 108 includes the subject matter of Example 104, and optionally,wherein the trigger message comprises an access barring indication tobar the UE from using a cellular link with the cellular node, andwherein the instructions result in controlling the UE connect to theWLAN, in response to the access barring indication.

Example 109 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in communicating between a cellular node and a User Equipment(UE) at least one Radio-Resource Control (RRC) signaling messageincluding an offload trigger to trigger the UE to start or stopoffloading to a WLAN.

Example 110 includes the subject matter of Example 109, and optionally,wherein the RRC signaling message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 111 includes the subject matter of Example 109 or 110, andoptionally, wherein the instructions result in transmitting the RRCmessage based on measurement information corresponding to the WLAN.

Example 112 includes the subject matter of Example 111, and optionally,wherein the instructions result in receiving the measurement informationfrom the UE.

Example 113 includes the subject matter of Example 111, and optionally,wherein the instructions result in receiving the measurement informationfrom another UE.

Example 114 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in transmitting from a cellular node a message including areselection frequency list including a plurality of Wireless Local AreNetwork (WLAN) frequencies of one or more WLANS, and a plurality of cellreselection priorities prioritizing the WLAN frequencies.

Example 115 includes the subject matter of Example 114, and optionally,wherein the instructions result in transmitting the message based onmeasurement information corresponding to the WLANs.

Example 116 includes the subject matter of Example 115, and optionally,wherein the instructions result in receiving the measurement informationfrom a UE, and transmitting the message to the UE.

Example 117 includes the subject matter of Example 115, and optionally,wherein the instructions result in transmitting the message to a UE andreceiving the measurement information from another UE.

Example 118 includes the subject matter of any one of Examples 114-117,and optionally, wherein the message comprises a Radio-Resource Control(RRC) signaling message.

Example 119 includes the subject matter of Example 118, and optionally,wherein the RRC signaling message comprises a RRCConnectionReleasemessage.

Example 120 includes an Evolved Node B (eNB) comprising a radio; and acontroller to control the radio to transmit to one or more UserEquipment (UEs) at least one Radio-Resource Control (RRC) configurationmessage to configure one or more measurements to be performed by the UEswith respect to one or more Wireless Local Area Network (WLANs), and toreceive from the one or more UEs one or more RRC report messagesincluding measurement information corresponding to the one or moreWLANs, wherein, based on the measurement information, the controller isto control the radio to transmit to at least one UE a RRC triggermessage including an offload trigger to trigger the UE to start or stopoffloading to a WLAN of the one or more WLANs.

Example 121 includes the subject matter of example 120 and, optionallywherein the RRC trigger message comprises a DLInformationTransfermessage, a RRCConnectionReconfiguration message, aHandoverFromEUTRAPreparationRequest message, a MobilityFromEUTRACommandmessage, a RRCConnectionRelease message, a RRCConnectionReject message,or a dedicated RRC message.

Example 122 includes the subject matter of example 120 or 121 and,optionally wherein the controller is to determine network assistanceinformation corresponding to one or more WLANs based on the measurementinformation, and to control the radio to transmit at least one RRCmessage including the network assistance information.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents may occur to those skilled in the art. It is, therefore, tobe understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theinvention.

What is claimed is:
 1. An apparatus comprising: a processor configuredto cause an evolved Node B (eNB) to: transmit a Radio Resource Control(RRC) message in a radio transmission to a User Equipment (UE), the RRCmessage comprising a measurement configuration information element toconfigure one or more measurements to be performed by the UE, themeasurement configuration information element comprising a WirelessLocal Area Network (WLAN) measurement object (MeasObjectWLAN) comprisinginformation of at least one WLAN, the measurement configurationinformation element comprising reporting criterion information andreporting format information, the reporting criterion information toindicate a criterion to trigger the UE to send a measurement report, thereporting format information to indicate measurement resultscorresponding to the WLAN to be included in the measurement report; andprocess a measurement report from the UE, the measurement reportcomprising the measurement results corresponding to the WLAN; and amemory to store the measurement report.
 2. The apparatus of claim 1,wherein the WLAN measurement object comprises at least one WLANidentifier to identify the at least one WLAN.
 3. The apparatus of claim2, wherein the at least one WLAN identifier comprises at least one of aService Set Identifier (SSID), a Basic SSID (BSSID), or an Extended SSID(ESSID).
 4. The apparatus of claim 1, wherein the WLAN measurementobject comprises WLAN band information to indicate a WLAN band.
 5. Theapparatus of claim 1, wherein the WLAN measurement object comprises WLANchannel information to indicate one or more WLAN channels.
 6. Theapparatus of claim 1, wherein the measurement report comprises a ReceiveSignal Strength Indicator (RSSI) corresponding to the WLAN.
 7. Theapparatus of claim 1, wherein the measurement report comprises anavailable admission capacity corresponding to the WLAN.
 8. The apparatusof claim 1, wherein the measurement report comprises a parameter basedon a load of the WLAN.
 9. The apparatus of claim 1, wherein themeasurement report comprises at least one WLAN identifier to identifythe at least one WLAN.
 10. The apparatus of claim 9, wherein the atleast one WLAN identifier comprises at least one of a Service SetIdentifier (SSID), a Basic SSID (BSSID), or an Extended SSID (ESSID).11. The apparatus of claim 1, wherein the measurement report comprisesWLAN band information to indicate a WLAN band.
 12. The apparatus ofclaim 1, wherein the measurement report comprises WLAN channelinformation to indicate one or more WLAN channels.
 13. The apparatus ofclaim 1, wherein the reporting criterion information comprises one ormore threshold values of one or more respective measurement reportingevents to trigger reporting the measurement results corresponding to theWLAN.
 14. The apparatus of claim 13, wherein the one or more thresholdvalues comprise a WLAN Receive Signal Strength Indicator (RSSI)threshold value.
 15. The apparatus of claim 13, wherein the measurementconfiguration information element comprises a Report ConfigurationInter-RAT (ReportConfigInterRAT) information element to specify criteriafor triggering an inter-RAT measurement reporting event, theReportConfigInterRAT information element comprising the one or morethreshold values.
 16. The apparatus of claim 1, wherein the measurementconfiguration information element comprises a list of measurementobjects (MeasObjectToAddModList) comprising the WLAN measurement object.17. The apparatus of claim 1, wherein the RRC message comprises an RRCConnection Reconfiguration (RRCConnectionReconfiguration) message. 18.The apparatus of claim 1 comprising a radio to transmit the RRC messageand to receive the measurement report.
 19. The apparatus of claim 1comprising one or more antennas.
 20. A product comprising one or moretangible computer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone processor, enable the at least one processor to cause an evolvednode B (eNB) to: transmit a Radio Resource Control (RRC)-message in aradio transmission to a User Equipment (UE), the RRC message comprisinga measurement configuration information element to configure one or moremeasurements to be performed by the UE, the measurement configurationinformation element comprising a Wireless Local Area Network (WLAN)measurement object (MeasObjectWLAN) comprising information of at leastone WLAN, the measurement configuration information element comprisingreporting criterion information and reporting format information, thereporting criterion information to indicate a criterion to trigger theUE to send a measurement report, the reporting format information toindicate measurement results corresponding to the WLAN to be included inthe measurement report; and process a measurement report from the UE,the measurement report comprising the measurement results correspondingto the WLAN.
 21. The product of claim 20, wherein the WLAN measurementobject comprises at least one WLAN identifier to identify the at leastone WLAN, WLAN band information to indicate a WLAN band, and WLANchannel information to indicate one or more WLAN channels.
 22. Theproduct of claim 20, wherein the measurement report comprises at leastone of a Receive Signal Strength Indicator (RSSI) corresponding to theWLAN, an available admission capacity corresponding to the WLAN, or aparameter based on a load of the WLAN.
 23. The product of claim 20,wherein the measurement report comprises at least one WLAN identifier toidentify the at least one WLAN, WLAN band information to indicate a WLANband, and WLAN channel information to indicate one or more WLANchannels.
 24. The product of claim 20, wherein the reporting criterioninformation comprises one or more threshold values of one or morerespective measurement reporting events to trigger reporting themeasurement results corresponding to the WLAN.
 25. The product of claim24, wherein the one or more threshold values comprise a WLAN ReceiveSignal Strength Indicator (RSSI) threshold value.